| 22 Oct 2025 |
 tomberek | Would it make sense for the final to be default if fetchTree has been given enough attributes? (If provided with all the info.) | 15:43:55 |
| 23 Oct 2025 |
 lovesegfault | First batch of small PRs to enable multipart uploads:
cc. John Ericson Sergei Zimmerman (xokdvium)
| 02:29:28 |
| lovesegfault | These are all tiny so it should be easy to review and merge. If you want to see the big picture, look at https://github.com/NixOS/nix/pull/14330 | 02:30:43 |
 fzakaria | I finished the Kaitai spec | 04:21:54 |
| fzakaria | https://github.com/fzakaria/nix-nar-kaitai-spec | 04:21:55 |
| fzakaria | it has test suite also | 04:21:59 |
| lovesegfault | y'all why is Headers not a map | 06:28:04 |
| lovesegfault | seems strange to use a vec of pair and force me to scan | 06:28:21 |
 Mic92 | I did some more work over the last weekend on the installer: https://github.com/NixOS/experimental-nix-installer/pull/51 i hopefully get ci green again this weekend and than i can do some more tests. | 09:56:46 |
 Robert Hensing (roberth) | is it possible to generate streaming parsers too? | 12:55:08 |
| Robert Hensing (roberth) | iirc http does not require unique headers, but that's only a reason to keep an additional vector around, if at all | 13:46:08 |
 Sergei Zimmerman (xokdvium) | In reply to @roberthensing:matrix.org
iirc http does not require unique headers, but that's only a reason to keep an additional vector around, if at all Multi map exists | 15:08:34 |
| fzakaria | I will ask. | 15:47:42 |
| Robert Hensing (roberth) | oh cool, thanks! I guess it could be pull based or visitor-like, or generate both | 15:51:39 |
| fzakaria | i don't see it in the current API but the generator has a few flags.
They call the API 'stream' lol
https://doc.kaitai.io/stream_api.html | 15:53:25 |
| fzakaria | maybe it is streaming and on-demand serialization | 15:53:41 |
| fzakaria | i will test it on the Linux demo. | 15:53:46 |
| fzakaria | * i will test it on the Linux git repo demo. | 15:53:52 |
| Robert Hensing (roberth) | ah, that's their low level I/O thing that is consumed by the generated code, I think? | 15:55:18 |
| Robert Hensing (roberth) | pull and visitor may be good names for modules that do that kind of thing | 15:56:16 |
| fzakaria | I used this cpp library which was nice.
https://github.com/NixOS/nixpkgs/pull/454770
I sponsor @jart on Github. | 16:01:30 |
| Robert Hensing (roberth) | fast? nice | 16:03:41 |
| fzakaria | also small so i can audit it
nlohmann's json.h has 24,766 lines of code. Our json.h has 233 lines of code, and our json.cpp file has 1,303 lines.
| 16:04:32 |
| fzakaria | oh there is an "no-auto-read" option | 16:27:41 |
| fzakaria | https://doc.kaitai.io/lang_cpp_stl.html | 16:27:42 |
 Philip Taron (UTC-8) | I'm getting a little lost trying to read through the argument parsing code. Can I land --extra-experimental-features anywhere in the Nix command line, or does it have to be immediately after nix or nix-build or whatever the appropriate entry point is? | 16:34:10 |
| Philip Taron (UTC-8) | Should I read AbstractConfig::applyConfig as allowing that to happen anywhere in the command line? | 16:35:17 |
| Robert Hensing (roberth) | Philip Taron (UTC-8): The command line code is rather involved, I agree. Most options can be specified anywhere, with the exception of after a -- separator (foo -- bar, note the space) | 16:39:22 |
| fzakaria | coulnd't figure out the auto-read; oh well for now the spec is still cool | 17:12:59 |
| Robert Hensing (roberth) | would be cool to have in the nix manual, like we're doing with JSON schema now | 17:26:47 |
