A lot of arc help is version dependent, contextual, configuration-dependent, or extension-dependent, and this trend will only accelerate in the future. arc help is accurate; Googling for stuff will often get you help for a different version/configuration. Usage documentation is already available online.

This report is very old and doesn't have reproduction instructions. If you're still experiencing issues, please file a new report by following the instructions in Contributing Bug Reports, including reproduction instructions (see Providing Reproduction Steps).

If you're using a closed-source IDE, you can change the IDE's behavior by working with the IDE's vendor.

I deployed this, seems to have worked properly in production.

Vaguely related: aphlict exited on notify001 with this error:

See Restarting Phabricator for detailed instructions on how to restart Phabricator after an upgrade.

It's entirely possible I missed some things in supporting the 25,000 different URI forms we now support, but just file a new issue if you run into anything since this task is now 200 years old with seventy pages of unrelated disucssion.

• D16852 should fix the coloring on the mobile month view.
• The icon means you're invited, not that other users have joined the event. Could we pick an icon that you'd find more clear? (Available Icons).
• Old events have undergone several migrations and probably aren't unambiguously fixable at this point, so I don't expect to correct any remaining migration issues.
• I can't reproduce the last issue you describe ("but are extended forward by a day on the event page"). Can you provide specific reproduction instructions?

Certificates have been deprecated in favor of tokens (they were less flexible, and users frequently found working with them confusing). Everything you describe is working as intended, so this is not a bug in Phabricator. We also don't provide support with third-party code.

Both 32GB volumes have been swapped for 128GB volumes.

D16115 + D16847 + D16848 make these changes:

I think that will prevent these edits from occurring by accident via the web UI. Yell if you manage to trick it or it causes any weird stuff.

This is way outside the realm of an upstreamable bug report with reproduction steps, but run this again:

Here's the raw data from that install:

Dragging a card on a workboard while in a priority-ordered view changes the global priority (see T8135). Mail tags in "other" groups are arbitrary, unclear, and going away (see T10448). I'm going to merge this into T10448.

(Also note that maniphest.edit is the preferred way to create and edit tasks in modern versions of Phabricator.)

There's no array_fuse() call anywhere near line 834 at HEAD of master, so I suspect this may already have been fixed in a more recent version.

I can't reproduce this. Here's what I did:

is Phab supposed to send email to users who are unverified?

I believe this is now in reasonable shape, in the sense that the overwhelming majority of prose inputs I'm aware of produce reasonable, human-readable diffs. They aren't perfect in all cases and aren't necessarily the diffs that a human would produce, but they're useful and fairly sensible.

That seemed to just work? Slightly disconcerting.

Look at how much engagement we're generating!

I would edit my comment to put a paragraph of text above the autoplay audio, but newsfeed caches the old comment. :3

I think we can safely conclude that autoplay audio in feed is an effective mechanism for disseminating important information.

Sure seems to be a lot of activity that generates feed stories on this task!