One issue I'm struggling with is that some daemon parsing is failing:

Actually, Phabricator uses static::class since D21744 and it works in older PHP per 3v4l.org, so I think I'm incorrect that this requires PHP 8.

See T13637. See T13588. In PHP 8.1, the behavior of static variables in methods changed, per this snippet from the PHP Documentation:

I do want $array[null] to kill the server in the general case so all the high-quality Phabricator code I write in the future can't do it, but I realize I may need to concede and silence the error. I am going to give up on this one:

also maybe copy https://we.phorge.it/D25387, which makes it so deprecation
messages don't kill the server.

• AWS now has over 800 instance types???
• I believe I've launched a new admin with a patched PHP that is surviving a least some of the deployment process. MySQL can't upgrade databases across major versions, so I'm restoring from backup now.
• @jmeador oh hi there
• @avivey Yeah, like half the pages are working for me while logged in but things are still pretty rough.

Hi Evan,

A wild epriestley appears!

Typical state-of-the-art software upgrade process:

General state of affairs:

Recent versions of Ubuntu default to a sudo implemented in Rust which doesn't support -E to pass the entire environment. A quick fix for this is to select sudo.ws as an alternative:

Multimeter was already locked down? Let's see if we can survive health checks now...

Related Phorge ticket: https://we.phorge.it/T15860 / https://we.phorge.it/D25696

(Of course, it'll probably just work the first time now...)

The export process is already robust at a coarse level: the dump is retained on disk and the process can be retried at the "upload the whole file again" level, then picked up with bin/host export using the --database or --database-file flags (probably with --keep-file).

The (anonymized) error the process encountered occurred while transferring the dump to central storage was:

Per above, this was partially mooted by the house framing rotting and partially resolved by me being generally pretty satisfied with the "Stop or Prop".

These are still stuck in a manufacturing backlog.

About a year later, I still like PCB manufacturing in theory, but haven't actually manufactured any more PCBs.

A year or so later:

I redid the clogged sink according to the schema above and haven't had any issues with it so far. I think this is probably an approximately reasonable map for tackling plumbing problems that might arise in the future.

For the moment, the customer has pivoted to knitting.

The customer requirement for "NO MUSIC!!!" abated before I got around to pulling the vehicle apart, so I'm giving up on this one.

Well now, that is certainly a nice rock.

See D21862.