Also, is static builds availability something that should block release? I'd be tempted to say it's a major regression tbf.
primops.cc
(Also: of your two options, I personally slightly prefer option number 1. There might be exceptions where I find number 2 better though, e.g. when the implementation of the primop is complex and…
primops.cc
Semi orthogonal, but to keep in mind while doing this refactoring: lix-project/lix#359
Someone who's willing to interact with the CppNix team should go ask them to better define their protocol, because right now it's a mess. There's nothing in the documentation which specifies…
And unlike content-encoding
and accept-ranges
, this can't be moved to writeCallback
because most redirects won't have a body and writeCallback
is never called for them. In case someone was…
Note: I'm not convinced that this is how Link
should work, and it would also be perfectly acceptable to consider this a bug and ask Flakehub to fix it server side, imo. Or the documentation…
This issue is very cursed and related to filetransfer.cc refactorings, most likely 86bfede948db03181cdf2989ee33b96905366f1b. In the CppNix version, Link
headers are taken into account at any…
Also reproduces in Nix 2.18.2 and 2.22.1.
For clarity since when you said "crashes" I expected e.g. a segfault or something:
$ nix repl
Lix 2.90.0-lixpre20240506-106b959
Type :? for help.
nix-repl> test = import ./test.nix
ni…
We discussed about this topic yesterday with @puck and one thing that came up is that entirely replacing aws-sdk-cpp with a custom implementation is likely out of the question. In particular, we…
I looked a bit into this and I feel like I now understand pretty well the issue. Essentially, the ^out syntax can only work on a derivation, since there is no way to go from an opaque store path…
Doesn't that seem premature when there is no evidence of harm from -O3? AFAICT all that has been reported so far is spurious warnings - all Lix tests are still passing.