Part of the additional delay was due to a custom patch I had to come up with to mitigate a DoS issue I discovered and reported to @Gargron. Still waiting on an official fix, but it should at least mitigate the issue for us until an upstream patch is available.
Fixed my biggest mastodon issue. When building the docker container, yarn frequently failed on a network request like this, " unexpected end of file", which aborted the docker build.
Fixed by adding the "--network-concurrency 1" option to "yarn install".
The fact that yarn doesn't handle graceful retries and lowering the number of threads is annoying.
# Why did it take so long?
The backup took a few hours, but what really killed it was the shitty yarn/codeload/npm registry networking problems. If we're having problems dl'ing a file, we should just give up the build process immediately. If the user wants to try again, they'll resubmit the job, riiiiiight?
I can fix this, but it means I need to stop being lazy and hook these builds up to CI and my internal registry, which I may or may not want to do.
What happened during the downtime?
# Full-vm backup
I don't do whole-vm backups (not snapshots) often due to the time it takes. The disk isn't large (500G), but it's not very sparse. I can fix this but it's tedious and I have to use DiskDestroyer to do it.
# Update mastodon to 2.4.1
I was waiting for the first point-release before updating, but we're now running the latest version of Mastodon.
Home to Producers and Fans of the
No Agenda Show Podcast If you have an issue please DM @email@example.com