I think this is fixed now, but let me know if it's still acting up.

It worked!

@paladox, please read the description carefully. The images are helping support the main point of the section, which is that Phabricator changes very quickly. Having old images which are very different from the modern UI helps reinforce this point.

I think this is now fixed (in the sense of "not broken anymore", not in the sense of "working as nicely as it possibly could"). Let me know if that's not the case.

See also T8597. Two specific areas for improvement:

Two fixes here:

To echo @chad's comments, we really want to drive accessibility changes by understanding problems and then solving them, just like we drive all other product changes.

yeah that does not make sense and would cause nothing to work I'm pretty sure

This parameter is not required, although the hint should probably say "optional order".

I believe this works currently, it's just not surfaced in the UI.

I have a repro for this if you don't.

Hm, in your original report the stack trace doesn't mention DrydockConstants.

Can you do this to get a stack trace?

I'm still seeing this errors.

I think I got all the incredibly dumb, incredibly easy stuff. Plenty of room left, but this install is feeling responsive to me again.

(I think this is fixed, but yell if it happens again.)

Manual runbook on this until we formalize the process, for hypothetical instance turtle:

Do you have rPc2a29338?

That stack trace is bonkers, I think we're calling tput cols every time we update a progress bar.

Phame is a prototype application. See this guide for more information:

I can not reproduce this.

We don't support HHVM. If you can't reproduce this problem on Zend PHP, you should report this compatibility issue to HHVM.

We aren't interested in pursuing changes with no upstream impact.

I ran this same command on a separate host and stopped the phd daemons before running the command. Doing so allowed the command to complete successfully.

Feed is doing some pretty silly stuff where it loads transactions, then loads their objects, then loads their handles (which loads their objects again), then loads the objects, then loads handles, which loads the objects again. In some cases, this loads objects about 6x more often than necessary. However, I think this is mostly specific to Feed, and it's not trivial to disentangle. I may take another look tomorrow.

Yeah, I find the exclamation icons to be too harsh (especially for the "accepted" state).