Hmm, for whatever reason, I’m on 2.31.4, so that might be the difference.
That version was tagged two weeks ago, because they apparently still release patch versions for rather old minor versions of nix. So, apparently I am getting updates, but I’m on some older release channel or something. No idea why.
I have to head to work now, so will have to debug in the evening or the weekend. Thanks for the clue, though.
I don’t think, we are doing different things. I create a new file, put {} inside, then add it into the imports = [...];. It gives me that error.
Then I git add ., run again and don’t get the error anymore.
Is the error you pasted now from some manual assertion you did?
Hmm, that sounds exactly like my setup. Weird.
I did have the file created, with {} inside (empty Nix expression). If I git add it, it works as well:
And yeah, I understand that it’s supposed to be a stacktrace, but other error messages look similarly horrendous and I can often only try to guess what’s wrong by reading the stacktrace top-to-bottom, so I’ve somewhat gotten used to doing that.
But good to know that these terrible error messages might be a problem with my system. Thanks!
Hmm, that’s interesting. For me, it looks like this:
I actually thought, it said somewhere in there, that the file isn’t staged, but apparently not even that (anymore?).
You don’t happen to be using Lix or something, do you? I’ve heard that it’s supposed to have better error messages, but I was never sure how much better it might be…
Edit: Perhaps I should add that those code locations it shows, are not from my code. Only the modules/terminal/new_file.nix in the second-last line is relevant.
I thought, you posted about the warning, because that’s actually easier to see than the error. Because yeah, it does say what you posted, but it’s in the middle of like 30 lines of other stuff. When I forget to stage a new file, it almost always takes me 5+ seconds to spot what the problem is. 🥲
Unfortunately, that shows up even when you’ve just modified an existing file, which is not a problem for it.
And which also happens to be the state my repo is in basically all the time, because I’ll change some setting, then see if it works like I want it to before making a commit…
Nice, that’s like the meme:
Look at how quickly AI put up a webpage for me: http://127.0.0.1/index.html
until some random AI agent
Wait, do they now have spam bots going around on random PRs to post advertisements?
Oh man, in general, people be raving about aliens, but never give two looks to the ants in their garden. Or you know, the entirety of Australia. Or the deep sea. We have so much life that’s alien buzzing around us. Hell, we even have the Scottish – humanoids that speak an entirely cryptic language. It’s so much more compelling story-telling, too, if they don’t arrive here in a spaceship, but rather have been living among us all this time.