This seems to be in relatively good shape. Some possible future work:

Another report of this over the weekend:
the test in https://secure.phabricator.com/diffusion/ARC/browse/master/src/repository/api/ArcanistGitAPI.php;0c9a03771961be79d09e566051a5a594866760d9$503-508
fails for non-English git, which makes repo detection fail (And shows up as "you can't close this revision" exception during arc land).

I believe T7879 is the root issue here, which will be resolved shortly in connection with T7707.

See-Also: https://phabricator.wikimedia.org/T493

My Phabricator instance started going really slow. The Dark Console revealed that all the configuration checks were running with every page load (e.g. git checks, pygments, etc). Further investigation showed that the APC was not working. After some helpful tips from @epriestley, I was able to fix it. Here's the blurb I added to my php.ini:

Thanks, D11906 should fix this.

administrator@ubuntu:/phabricator/phabricator$ ll /var/tmp/
total 12
drwxrwxrwt 3 root root 4096 Feb 27 18:32 ./
drwxr-xr-x 14 root root 4096 Oct 24 18:31 ../
drwxrwxr-x 4 phd-user phd-user 4096 Oct 23 14:46 phd/

haha, thanks @joshuaspence

@anton.vladimirov this should have been resolved by the commits here, not sure what more information you can give us why that didn't occur.

@anton.vladimirov, what are the permissions on the /var/tmp directory?

Make sure that ALTERing a binary collated column which contains utf8mb4 characters into utf8 column succeeds with --unsafe.

This is relatively simple to fix, but we need to:

LANG=en_US.UTF-8 should do the trick, but it fails if the en_US.UTF-8 locale is not generated/available.

Thanks @fabe.
I resolved that issue after search init and change mysql config ( STRICT option ).
It works well but I found T6892.

just run

./bin/search init

first.
This will create the needed elasticsearch index.

Thank you for your answer. But I met this error message.
after "search index --all"

[HTTP/404] Not Found
{"error":"IndexMissingException[[phabricator] missing]","status":404}

Is it need more configuration for this?

https://secure.phabricator.com/T5282#62676

Is there a temporary way to resolve this issue? ( Just only for wiki search )

Thanks very much. I'll update this evening.

that's $10 for support buddy

You need to set notification.enabled to true in your config.

(whoops, forgot to RTFM... https://secure.phabricator.com/book/phabricator/article/notifications/)

If I run

Although I don't think this is particularly important, landing some version of D10063 is probably worthwhile since people who try to use it often end up pretty blocked in reasonable use cases. It's only blocked by it being kind of a pain to set up and test.

I think we can remove Support Impact from this. I've seen fewer setup/install-realted issues recently, and imagine this is going to be a long-tail task with a lot of ongoing tweaks that probably should happen post-Phacility.

What's next here? This seems like a good one to get done close to the Phacility launch and / or iterate on soon after?

Closed by commit rP384b670709aa.

Closed by commit rP08126d39049e.

I went so far as to re-install Phabricator from scratch and was able to successfully fully import the Phabricator repository again.

I think its theoretically possible to build perfect software that has zero support costs though I'd bet this will never be achieved by any team of humans. Relatedly, I do think its possible to build many things to reduce support costs.

One concern about this is that this information is policy-bypassing.

Please check https://secure.phabricator.com/maniphest/report/project/

We had no herald rules it was a clean start.

I was holding off marking this as resolved to 1) wait a bit to fix the bugs as they came in and 2) clean up some reverse paging code.

Yes, everything is fine. Just an FYI that importing the commits into Phabricator is done via the various worker parsing...

Closed by commit rP2fedb6f941d8.

The issue is not to import the commits into phabricator. But when the workers start to parse the commits for "whatever". If you go to the deamons task list is everything fine ?

Thanks for the fix :)

I think I broke and fixed this doing some related work in the area as I did all sorts of things to the low-level transactions framework around when this was reported.

I do not know how to reproduce this issue as reported. For example, I import the Phabricator production instance into my local dev install. I do have a btrahan account there, but otherwise there is no user account overlap. Commits seem to import fine:

Closed by commit rPe76499bbbb62.

Thanks for getting this so fast, we'll be sure to pull this into our next deployment.

Closed by commit rP8ac73b2bf351.