-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infinite recursion encountered #561
Comments
Try setting Maybe this is related to #419. |
Just gave that a go, unfortunately I am still getting the same infinite recursion error. |
I ran into that same infinite recursion error. I found that holding nixvim back on an older version prevents it. Are you using also nixvim and could it be conflicting here? |
Thank you! I do use nixvim, and indeed reverting to a previous commit fixed the infinite recursion issue. Specifically, it seems that this specific commit is where the error begins, which makes sense as it does mention infinite recursion as a potential problem across the commit description and code comments. My nix proficiency is far too low to understand why this commit leads to an infinite recursion, specifically when you have a stylix NixOS configuration enabled (I tried forking nixvim to figure it out, but didn't really get anywhere). I'll close this issue for now as it seems like more of a nixvim issue and than a stylix issue, but I very well may be wrong so feel free to re-open it if that's the case! |
I recently updated my flake inputs and encountered an infinite recursion error when attempting to rebuild my system. After some troubleshooting, I found that removing the NixOS stylix module from my config fixed the error. My home manager stylix config seems to be fine.
I am not sure what is responsible, but I have tried the following troubleshooting steps:
None of these steps were successful. Below is my NixOS stylix config and the full trace.
/modules/nix/stylix/default.nix
Trace: https://gist.github.com/kay-mw/acc5e6751abf18b6cc3eff5e1385bd4b
The text was updated successfully, but these errors were encountered: