!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

485 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.152 Servers

Load older messages


SenderMessageTime
30 Jun 2026
@arianvp:matrix.orgArian
In reply to @arianvp:matrix.org

I found a corrupt gnugrep nar I think?

https://cache.nixos.org/srk76h64a1ja4z7njh5lxcds7m9hnc7y.narinfo

Says file size 248729 bytes
But when i download i get 248412 bytes

The FileHash also doesn't match

Interestingly the NarHash does..

Race condition of uploading the nar + undeterministic compression?
07:56:04
@vcunat:matrix.orgVladimír Čunát Do you still experience it? I now did nix build /nix/store/srk76h64a1ja4z7njh5lxcds7m9hnc7y-gnugrep-3.12 and it passed. 07:59:00
@vcunat:matrix.orgVladimír Čunát * Do you still experience it? I now did nix build /nix/store/srk76h64a1ja4z7njh5lxcds7m9hnc7y-gnugrep-3.12 (the path shown in that .narinfo) and it passed. 07:59:21
@dramforever:matrix.orgdramforeverpossibly had the positive narinfo cache for the old one?07:59:40
@arianvp:matrix.orgArianSo it fetches just fine in nix. But the FileSize and FileHash in the narinfo are wrong. I guess nix ignores those fields?08:03:50
@arianvp:matrix.orgArianBut if they're ignored why do we have them.08:03:58
@arianvp:matrix.orgArian* But if they're ignored (and wrong) why do we have them.08:04:16
@dramforever:matrix.orgdramforeverthey aren't normally wrong...08:05:46
@dramforever:matrix.orgdramforeveroh huh08:07:43
@dramforever:matrix.orgdramforeverit really is still wrong08:07:47
@vcunat:matrix.orgVladimír Čunátzstd should be deterministic, though: https://github.com/facebook/zstd/issues/2949#issuecomment-99975019108:18:06
@joerg:thalheim.ioMic92 vcunat: I think the lengh is not 08:18:31
@joerg:thalheim.ioMic92 * vcunat: I think the length is not 08:18:38
@joerg:thalheim.ioMic92this is an artifact before I introduced: https://github.com/NixOS/hydra/commit/4e36de08453e62cb850a5c5f70d75afcea711cda08:19:34
@joerg:thalheim.ioMic92Fixing that requires going through a week or so worth of narinfo...08:19:57
@vcunat:matrix.orgVladimír ČunátIf fetching by nix doesn't get broken, it's not terrible maybe. Also if no FODs got affected (?), all these NARs would get "outdated" within a few weeks.08:23:15
@arianvp:matrix.orgArianI wonder if we can fix by constructing by just setting the Content-Encoding header on the nar object as opposed of storing a Compression field in the narinfo file08:24:16
@joerg:thalheim.ioMic92Yeah. that's also why I didn't priotize fixing it yet. I rather want to spent the time on getting my hydra commits back into master and than look into gc08:24:18
@arianvp:matrix.orgArianThis makes the whole thing atomic. 08:24:22
@arianvp:matrix.orgArian* I wonder if we can fix by construction by just setting the Content-Encoding header on the nar object as opposed of storing a Compression field in the narinfo file08:24:37
@joerg:thalheim.ioMic92* Yeah. that's also why I didn't priotize fixing it yet. I rather want to spent the time on getting my hydra commits back into master and than look into cache.nixos.org gc08:25:25
@joerg:thalheim.ioMic92Nix should be able to consume it, maybe some other tooling would need an update to look at Content-Encoding, also the same tooling already needs to do this in other places anyway.08:25:49
@arianvp:matrix.orgArianBoth nix and lix definitely support it. As snix's nar-bridge uses content-encoding and I haven't had any issues pointing lix at it recently 08:27:17
@arianvp:matrix.orgArian(there were some at the beginning)08:27:26
@vcunat:matrix.orgVladimír ČunátIs perhaps HTTP 416 related? https://github.com/NixOS/infra/issues/110608:27:45
@joerg:thalheim.ioMic92One wrinkle is that this idempotent header only exists on AWS, so for general s3 support it would be nice to switch this.08:27:50
@joerg:thalheim.ioMic92it's an .xz url, so maybe some older issue?08:28:33
@vcunat:matrix.orgVladimír ČunátOh right 🤦08:28:53
@arianvp:matrix.orgArian
In reply to @joerg:thalheim.io
One wrinkle is that this idempotent header only exists on AWS, so for general s3 support it would be nice to switch this.
Im not understanding what you mean by this
08:33:20
@joerg:thalheim.ioMic92 Arian: I haven't seen other s3 implementations that also support 'If-None-Match: *' header 08:34:18

Show newer messages


Back to Room ListRoom Version: 6