libuv: Intermittent trouble with dist.libuv.org

I’m going to close this, looks like we are good!

We aren’t able to build our application because of this issue… it’s been causing quite a bit of stress. Looking forward to the fix.

Alright, that was a bit easier than I thought. I added a metadata cache so now the dates show correctly even for directories.

Our production deployments are failing due to this outage. Please, help!

SGTM! I’d set the DNS record’s TTL low for now, in case we need to switch back in a hurry.

@saghul That’s looks like a nice solution you worked out there

No worries, Ben got the files.

Quick test GH Pages thing: https://bettercallsaghul.com/dist-libuv-test/ source: https://github.com/saghul/dist-libuv-test

I’m open to contracting if you’re in a rush to get this fixed, otherwise it’ll be when I have time this week.

I should mention that what we do in some (but not all) of our CI/CD jobs is building libuv from the source distribution that we download and verify from the website. Other jobs get libuv from a Linux distribution, or from GitHub with git, or from GitHub by downloading a zip.

We do this to verify our documentation - if you can’t actually download libuv from dist.libuv.org and build it, then we don’t want to be telling users they should be doing that in documentation.

So, it’s not a showstopper (because it eventually works), but we have to re-try the pipelines several times due to the failures, so it slows things down.

Of course, we can cache libuv locally, but that’s not something that I want to make a habit of, because it just hides the problem. Our process must work because it is how I noticed it was having trouble again.

Edit: So, if the files could stay in the same place, that would be best, no changes to third-party documentation or CI rules.