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!

Welcome to the wonderful, spooky world of Quicksand.

We still do a pretty questionable job on the first case in T7643#180264, where a comma is removed from the middle of a sentence.

Do you have the persistent chat pane open?

Would you fill out at least, like, 5 of them?

Yeah, I think it's pretty reasonable if people would actually fill it out. We could surface it in a few other places too (e.g., /projects/) without fallback. It just seems like there's a decent chance no one will ever fill it out and it will sort of just be cluttering up the UI. But the cost on our side is pretty small, so if some people claim that they'd probably want to fill it out I'm happy to move forward with it.

For reference, here's the current state of "discovery" downstream:

I'm going to kick this out of the queue for now and we'll reconsider it alongside other internal priorities once the queue clears. I think it's probably secondary to Conpherence now, at least, product-roadmap-wise, maybe?

I'm going to kick this out of the queue for now and we can re-evaluate our internal priorities once the queue clears -- we got a decent iteration out and it looks like the next steps on NUX are probably a fair chunk of work.

The driving install dropped off the grid a while ago, so this is no longer prioritized.

I believe this is now resolved, in the sense that I expect all specific, reproducible examples I'm aware of function in a way consistent with user expectation. In particular:

I have some possible approaches for cheating on the "more than 100 results" case, but I think we ultimately need to put the prefix paging rule on the server side, so we return all prefix matches and then all content matches. That's kind of a big mess, but all the ways we can cheat will break down at some point (e.g., when you have 100 "wikidata" projects that are alphabetically earlier than "wikidata") so I think it's not avoidable.

• Prototype applications must be enabled.
• security.outbound-blacklist must not blacklist the target server (build servers may be on an internal network and on the default blacklist).
• The link protocol must be "http" or "https".
• You must not have exceeded your fetch quota for the last hour.
• You must have file storage configured.
• The image MIME type must be part of files.image-mime-types and files.viewable-mime-types.
• The Phabricator server must be able to make outbound requests on the network.

Pausing this from our perspective since we're waiting on guidance to move forward.

Presuming this is resolved since it hasn't been updated in about a month, but let us know if it's still an issue after the update.

D16837 should clean this up. Thanks for the thorough report!

Some discussion of current context in T10448#186240.

Oh, no, T7579 / T7580 are very slightly different. These probably do need updates at some point but I'll leave 'em for now

I'm going to merge this into T7580 since I think that's the same task?

I added "Mentions" (and "Mocks") recently in connection with T4788.

This is sort-of-maybe related to T11482 but I'm also not exactly sure what's step in the process is slow here.

I'm happy to change this if anyone comes up with good alternate wording, but I think this might be about the best we can do.

never mind I love the text area