no description only meoww


fullmoon
@fullmoon

A large number of unsigned /nix/store paths were uploaded to an S3 cache by mistake and it turns out that this is EXTREMELY difficult to fix. Moreover, these unsigned paths represented several really expensive build products (including ghc and all of its reverse dependencies) and they permanently poison the cache until fixed. This brought development on the tip of our master branch to a standstill today, but fortunately I was able to fix it.


leftpaddotpy
@leftpaddotpy

holy shit lol

i think that Nix hasn't been thoroughly tested with some of that tooling....


You must log in to comment.

in reply to @fullmoon's post:

I feel like this kind of decentralized client poking a dumb stateful service stuff is rather terrifying. Imagine poking the production database from your computer or something. Especially when the code in question is, like Nix, following contribution processes that are both dubious and stalled.

I miiiight have a connection to work's production db on my development computer. I haven't broken anything yet at least. It is useful for debugging production >//<. At least I have it use read-only credentials most of the time. The times where I needed to use non-readonly credentials were when I needed to do stuff like manual one-time vacuuming or when the bugs are extra nasty.