| 16 Oct 2025 |
 John Ericson | Robert Hensing (roberth): when you did one big file, did you use 1$defs? | 16:47:36 |
| John Ericson | * Robert Hensing (roberth): when you did one big file, did you use $defs? | 16:47:40 |
 Robert Hensing (roberth) | You mean this? https://github.com/nixops4/nixops4/blob/dd10dd638a4a2b7f5912ea89076e719593f230db/rust/nixops4-resource/resource-schema-v0.json#L6 | 17:08:26 |
| Robert Hensing (roberth) | * John Ericson: You mean this? https://github.com/nixops4/nixops4/blob/dd10dd638a4a2b7f5912ea89076e719593f230db/rust/nixops4-resource/resource-schema-v0.json#L6 | 17:08:34 |
| John Ericson | Robert Hensing (roberth): yeah | 17:09:05 |
| John Ericson | supposedly that tool supports multiple separate json files with one invocation | 17:09:24 |
| John Ericson | have you tried that? | 17:09:26 |
| Robert Hensing (roberth) | oh interesting | 17:10:05 |
| Robert Hensing (roberth) | I didn't need it | 17:10:30 |
| John Ericson | Sergei Zimmerman (xokdvium): btw (just so you see it here) I am trying to see if this tool can do cross-file references for json schema now | 17:26:30 |
| John Ericson | but I don't have high hopes | 17:26:34 |
| John Ericson | Robert Hensing (roberth): you had to provide a root , it couldn't just be definitions, for single file version? | 17:26:58 |
 fzakaria | 21x speedup for nix nar cat | ls
https://github.com/NixOS/nix/pull/14273 | 17:27:13 |
| fzakaria | there is so many abstractions in the codebase | 17:28:26 |
| fzakaria | hardest part was figuring out which to use :P | 17:28:31 |
| fzakaria | thankfully someone already made makeLazyNarAccessor so the work was easy :P | 17:28:46 |
| Robert Hensing (roberth) | I think I had to. You could have a tiny file that imports stuff, but it's not aware of other files to link to in the output, afaik | 17:32:11 |
| Robert Hensing (roberth) | You can just put a big oneOf in the root | 17:32:39 |
| John Ericson | Robert Hensing (roberth): OK I think I got in a state I like it | 19:30:40 |
| John Ericson | how do we review it? :) | 19:30:43 |
| John Ericson | * how do we review it? cause after making a bunch of changes I don't think I should just merge it :) | 19:31:03 |
| John Ericson | I made the hash serializer a second commit for a future Pr | 19:31:20 |
| John Ericson | this one just does the derivation serializer | 19:31:27 |
| John Ericson | but it still has multiple .yaml files | 19:31:34 |
| John Ericson | and so we make sure that the cross-file references work | 19:31:52 |
| John Ericson | (I made a WIP hash one just to factor out hashAlgo from the current DRV json format there) | 19:32:14 |
| John Ericson | Eelco: https://github.com/NixOS/nix/pull/14272 this ones make me smile, because that serializer stuff was one of the first refactors I did, and now I think you are on the cusp for finding the "killer app" for it :) | 19:37:39 |
 raboof | Hmm, I'm noticing since a ~recent nixpkgs update, OUT_PATHS doesn't seem to be passed to the post-build hook anymore. I haven't done a proper bisect yet, I did browse the code/issues/PRs a bit but didn't see anything that jumped out at me. | 20:53:44 |
| fzakaria | as a follow up to https://github.com/NixOS/nix/pull/14273 maybe someone wants to pair on working on RemoteFSAccessor
It also stores the NAR fully in memory as a std::string
Would be cool to remove the std::string constructor from NARAccessor completely. | 22:13:28 |
| fzakaria | if you write an issue i can look into it | 22:16:53 |
