In reply to @d4hines:matrix.org
I've read through some of the Nix pills and I've gotten DevOS working, and that's about it. It's quite a learning curve

In reply to @blaggacao:matrix.org
Honestly, I don't find the nix-pills super useful. But I guess we don't yet live up to rust standards in terms of docs 😃🦧

In reply to @d4hines:matrix.org
Do you have any recommendations on how to get to "journeyman status" in Nix?

In reply to @blaggacao:matrix.org
So I look at the backtraces and place a few traces in nixpkgs to understand what's really going on and then use that modified version of nixpkgs as an input.

I find some common patterns that reliably cause infinite recursion:

• careless use of rec in overlays
• computation directly in an import

Both of these can be easily solved by using a let binding instead. Whenever I find infinite recursion and I can't trace it back to my local changes, i.e. tons of nixpkgs traces, I just start commenting stuff out until it works, and then work backwards from there 😅

In reply to @timdeh:matrix.org

I find some common patterns that reliably cause infinite recursion:

• careless use of rec in overlays
• computation directly in an import

Both of these can be easily solved by using a let binding instead. Whenever I find infinite recursion and I can't trace it back to my local changes, i.e. tons of nixpkgs traces, I just start commenting stuff out until it works, and then work backwards from there 😅

I can complement:

• Similar to rec, it can also happen with overlays and "recless" crossing of prev and final dependency.
• Using flake self outside of an output value seems to cause that too.