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.

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. It wasn't designed in from the beginning and that results in limitations where compromises were/are necessary. Unfortunately, this means users sometimes end up with unexpected or unintuitive behaviors. I think we're all just trying to find ways to mitigate them.

A related score-board might be to show mana-rich tasks.

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.

This was more fun than expected. Notes for future historians:

Doing this now.

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

Here's an example:

Sure, will do this afternoon.

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

This appears to still be open.

@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:

The workaround does not work for me on Debian 9.5 with OpenSSH 7.4p1. Actually I am surprised this worked for anyone, since the issue appears to be that the buffer of the pipe between ssh-auth's stdout and the parent's stdin is being filled, hence ssh-auth blocking at some point. It should not matter how fast these buffers are being filled...

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

Looks like CircleCI will stop supporting the V1 API, which we use, in about 5 weeks: https://circleci.com/sunset1-0/

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.