addErrorContext frames are always printed in backtraces now, even without --show-trace

I’m extremely hyped about this one. Evaluation errors are finally actually useful!
I previously always used --show-trace but it generates a full back trace which includes lots of irrelevant text like module system implementation details.

score 1 · canonical

I was hoping to try it out again recently, but found the BLAKE3 hash experimental feature that I have been using is waiting on something to be rewritten in Rust? Is there a branch or a patched in version?

score 1 · canonical

The experimental RPC protocol is now shipping under the rpc-sockets experimental feature. As one may guess this is still highly experimental and must be enabled not only with the experimental feature flag in your Lix config

so it’s production-ready?

score 1 · canonical

always excited to read these release notes, if only to be reminded there are teams who really care about software quality still putting stuff out. great work!

score 1 · canonical

This surprising behavior was commonly seen when nix store delete was called with a path that was not present in the store, causing the path to be downloaded just so that it could be deleted.

I think I saw something like this mentioned in a previous release, but it’s still one of my favorite funny bugs.

score 1 · canonical

I upgraded, but my remote builder stopped working. My user is a trusted user. Has anyone else encountered this problem?

score 1 · canonical