Is this a bug report?

I updated to get rP9d125b45 and there is no change. Cloning a repo using http still hangs. I then reverted the change in rP8269fd6 and that did not fix the problem either.

I'm unable to reproduce this against this host or hosts in the Phacility cluster.

Tested with rP9d125b459ea8, and it's working properly: thanks for the quick fix!

Seems like once you mess with the order of the tabs, the default doesn't work.

Nice. This is likely something easy/simple/silly, I just haven't been able to reproduce it locally and the answer has yet to come to me in a dream.

I have a repro in my sandbox, will dig around.

ip2long can also return negative values (see rP30473549).

Ah, thanks! I think you are right, that is the problem.

This was almost certainly fixed by 5a723bf (D14991 / T10116) on January 11.

Peculiar -- this behavior doesn't exhibit here, but I just did the same thing of removing a subscriber and using Cmd+Enter (screenshot of that: https://www.dropbox.com/s/qp8tyxrh7mq86xa/Screenshot%202016-02-02%2007.07.46.png?dl=0) and the action was not taken.

We're using 2015 W52 -- I checked the changelog since, didn't see anything that seemed relevant.

I have encountered the same issue in one out of about 7 projects. The only thing i seems to remember doing is setting it a few times to different pages while it was working, until it stopped.

Ok, thanks, note that this problem is probably the same as this one: T7260
But it seems to be easily reproducible with linux repo.

Nevermind me, Google suggests IPv6 a pain in PHP

Which server log are you asking about? I have looked around at various logs and can't find any errors, but maybe I'm not looking in the right place. I see the GET and POST commands, both returning 200, in the nginx logs and that is it. Nothing in syslog.

What version of Phabricator are you running?

• Do you see any errors in the server log?
• Are you sure about adding @v1.2.15 to the clone uri? I've never seen this before.

FWIW, PHP 7 is not yet supported.

I'm using PHP 7.0.2 with nginx 1.8.1, and running Phabricator at HEAD:

Not sure if lisk should interpret "false" as "null" in this case?

In T10257#156493, @epriestley wrote:

Broadly:

• You only need to run arc liberate when developing Phabricator itself (e.g., writing Phabricator extensions or otherwise modifying Phabricator).
• The one ARM system (the Raspberry Pi) we have other direct evidence of users attempting to do installs on is explicitly not supported as a Phabricator host platform -- see Installation Guide. You can try, but you're on your own.
• If you're using an ARM system that could, in theory, broadly qualify as a "normal computer" to host and/or develop Phabricator this is something we might eventually look at supporting, but we don't currently have any evidence that anyone else is trying to do this. We are vanishingly unlikely to dedicate resources to ARM support for the benefit of only one user (if you are developing on ARM hardware) or one install (if you are hosting on ARM hardware).
• If you did read the "Installation Guide" and believed ARM hardware to reasonably qualify as "a normal computer", we can add additional language to make it clear that ARM is not included in what we consider "a normal computer".

I can reproduce some variant of this locally by following these steps on OS X:

Ah, thanks. I think this is almost certainly related to your keyboard layout and how we're detecting that you typed "@".

I tried it again with a fresh win10 install and the latest chrome version. Again no username autocompletion.

I cloned Linux and examined the commit, but couldn't immediately see anything wrong with it. I'll do the full import when I have a chance.

There are some errors in the log, but they seem unrelated:

Anything in your PHP error_log?

Unfortunately it doesn't. I get the confirmation popup in a separate window, click Make default and I am redirected to the settings screen without the setting being saved.

@OCram, do you have an non-US keyboard?

• You only need to run arc liberate when developing Phabricator itself (e.g., writing Phabricator extensions or otherwise modifying Phabricator).
  • The one ARM system (the Raspberry Pi) we have other direct evidence of users attempting to do installs on is explicitly not supported as a Phabricator host platform -- see Installation Guide. You can try, but you're on your own.
  • If you're using an ARM system that could, in theory, broadly qualify as a "normal computer" to host and/or develop Phabricator this is something we might eventually look at supporting, but we don't currently have any evidence that anyone else is trying to do this. We are vanishingly unlikely to dedicate resources to ARM support for the benefit of only one user (if you are developing on ARM hardware) or one install (if you are hosting on ARM hardware).
  • If you did read the "Installation Guide" and believed ARM hardware to reasonably qualify as "a normal computer", we can add additional language to make it clear that ARM is not included in what we consider "a normal computer".

I found the project ID with that method link
The bug can be closed, thanks to all of you !

Can't reproduce on any Windows nor any Chrome versions. (Win7, Win8, Win10), Chrome 48, 49.

Is the local system a raspberry pi?

The project's hashtag.

Thank you!
I was sure there is solution like that.
But what abbreviation is for Project object ?

You can use bin/policy unlock to unlock an object.

I can't reproduce this.

• Tested with Chrome 48.0.2564.97 on Windows7

I will try it this evening on different client platforms and check whether it has something to do with our enterprise proxy or firewall.

I can't reproduce this with Chrome 48.0.2564.97 on OSX. Here's the autocomplete working on my local instance in Chrome:

Yeah, I agree that these are pretty confusing in typeaheads. They kind of ended up there by accident, I'll swap them back to always being fa-user in that context.

yes it's fixed. thx for the fast response.

Should be fixed at HEAD. Thanks for the report!

i just did a simple git pull like every other update

@chad, I'm going to push this back down to PHUIHandleTagListView.php and rename it:

Sounds like this might be a PHP version issue, are you using one older than 5.5?

Can you provide details on reproducing the errors? My sandbox and this install are both at HEAD.

User defined symbols probably shouldn't be shown on any typeahead.

You're welcome. Thanks for the quick fix.

Thanks for the report, should be fixed at HEAD.

thanks, fixing.