| 16 Oct 2025 |
 BMG | I'm spending my afternoons on this stuff at the min. I'm gonna grab some lunch and dig into this properly. Need to brush up on my clickhouse skills a bit. | 11:51:58 |
| BMG | Might be faster to just finish the postgres import process and poke around it there, cos I'll have parsed the narinfos and have the references etc and be able to relate the nar entries to the nar infos | 11:53:20 |
| BMG | 🤔 | 11:53:30 |
 vcunat | narinfo is per derivation. nar is per derivation output. Am I wrong? | 12:01:57 |
| BMG | 🤔 | 12:02:09 |
| vcunat | We do use multi-output derivations pretty commonly, at least in the more-core packages. | 12:02:26 |
| BMG | That would make sense | 12:02:44 |
| BMG | But woudl that mean more nars than narinfos? | 12:03:17 |
| BMG | * But wouldn't that mean more nars than narinfos? | 12:03:25 |
 hexa (signing key rotation when) | yes | 12:03:31 |
| BMG | We're seeing the opposite | 12:03:45 |
| BMG | If my clickhouse skills are to be believed | 12:03:51 |
 raitobezarius | <confusion intensifies> | 12:04:02 |
| vcunat | Ah, I misread that. OK. | 12:04:20 |
| vcunat | It does happen commonly on Hydra that we build the same-hashed derivation twice in parallel. | 12:06:02 |
| vcunat | * It does happen commonly on Hydra that we build the same-hashed derivation twice in parallel (and both succeed). | 12:06:09 |
| vcunat | I'm not sure what exactly happens in that case. But even so. | 12:06:26 |
| BMG | which would account for same nar but multiple narinfos? | 12:06:29 |
| BMG | assuming the build output was bit-wise reproducible | 12:06:48 |
| vcunat | They often are not, but I'm not sure that really affects the count of re-uploads. | 12:07:23 |
| vcunat | It doesn't affect the (S3/URL) paths. | 12:07:39 |
| BMG | Happy to jump on a call a bit later and poke through this dataset together | 12:15:23 |
|  ·☽•Nameless☆•777 · ± joined the room. | 13:40:10 |
| ·☽•Nameless☆•777 · ± | Hi o/ | 13:41:21 |
 Mic92 | In reply to @brian:bmcgee.ie
But wouldn't that mean more nars than narinfos? You can end up with more narinfos if you produce the very same build-output. | 15:13:26 |
| Mic92 | Ah vcunat said this already | 15:13:48 |
 dramforever | i am pretty sure this is wrong | 15:14:38 |
| dramforever | narinfo is per path, nar is whatever | 15:14:44 |
| dramforever | so you'll have one narinfo per output | 15:15:15 |
| dramforever | protocol-wise the nars doesn't matter, you just need to point the URL in narinfo to something | 15:16:15 |
