A couple days later than planned at is got stuck into the inbox of my scatterbrain self, here’s the last update from the Tweag Nix team (following the previous one here).
The call for testers of content-addressed Nix got quite a bit of success.
A fair number of people tried it, reporting a number of issues and − suprisingly - several managed to fully build a content-addressed system.
- The most annoying issue spotted was #4806 (also appearing as #4775 and #4513) which got fixed by #4776;
- Because of an extra
/in the urls, s3 buckets didn’t use to work. This is now fixed by #4767;
- Remote caching was also painfully slow because contrary to the narinfo files, the realisations (or lack of) wasn’t cached locally. #4781 now fixes this;
nix runalso crashed, and got fixed in #4819
A number of these new small (or not) issues are still open, like #4823 (
nix develop crashing), #4821 (
nix-shell not doing the right thing), #4820 (
nix-store --query failing under some specific circumstances).
Fixes are on the way, but if you want to help making this faster, feel free to chime in in #nixos-dev or #nix-ca and @regnat will be more than happy to point you to the right place to start.
As promised last week, @yannham gave a talk about Nickel at LambdaJam.
is available on youtube, go check it out, it’s worth it! was available on youtube, but the conference organizers have unfortunately made it private.
He also worked on the load-balancing part, which is the final missing part for having a federated Trustix.
Last, but not least, the project got accepted for a second NGI grant, meaning that @adisbladis will be able to continue working on it for several months at least.
With nearly a hundred (!) candidates, the application period for the summer of Nix finished a few days ago.
The team now has to deliberate to select the participants.
And that’s all folks!