T13182 was a resurgence of this exact issue, but I'm currently banking on the fix being a move to Ubuntu 16 with T13076 before this breaks again, given that it was stable for ~18 months.

That appears to have fixed it, so this was just T12171-redux.

It feels like the basis of the problem is that linting was written well without autofix in mind and then the feature was added later.

One specific thing we hit in the context of T13180: sbuild001 stopped and started with a new public IP, and the Almanac device record needed to be updated with the new address.

See PHI790, which reports an inconsistency in reporting between APCu and APC that possibly points at a more significant issue.

re-archetect the patch application to operate per linter or per issue rather than after completing all analysis

Your desired behavior is to emit multiple conflicting patches, then prompt the user to choose between them?

@amckinley, do you want to take this one whenever you get a chance? This seemed to work the last time:

See PHI801. This is a similar case to the one above, but I think the underlying use case was a bit more compelling: the install was transitioning from a set of older web nodes to newer web nodes as a part of a general infrastructure upgrade, and making various fixes to the deployment and support software as part of that process. One aspect of these adjacent fixes was changing the path from /something/something/phabricator to /something-else/something-else/phabricator (I think as a consequence of adjusting deploy strategy), so newer nodes would have a different absolute path than older nodes. Both sets of nodes were in production simultaneously.

(Just merge this into T13156 if that makes sense?)

An instance manager created a mailing list named avivey with your email address:

On SMS MFA, Reddit got bitten recently by SMS having poor security properties:

We have a more reliable break for this now, in the form:

I kicked a couple things out and moved the rest to T13164 to sort of force things back on some kind of normal-looking track with a plausible connection to realtime.

I'm descheduling this out of T13151 since none of this is too burning and it's grown kind of big. Probably makes more sense after T13076 as we move toward private clusters, since these UIs will need updates anyway.

I've marked D19541 as resolving this. The change there isn't quite what was asked for here, but overlaps significantly.

See also PHI786 for an example of a general issue: voiding invoices is currently inconvenient: there's no actual "void" state for invoices so you have to go hunt them down manually and DELETE them. There should be a formal "Void" state they can be kicked into.

I can't get anything to break at all now. 💁