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…
Yeah, I was gonna say, that might be the root cause.
In the vast majority of cases, you want Box<dyn Error + Send + Sync>, but folks tend to leave out the Send + Sync, because it looks like additional complexity to them, and because it doesn’t cause problems when they’re not doing async/await.
It’s better to define a type alias, if you don’t want that long type name everywhere.
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?
I’m not much of a fan of Debian, but in your position would still recommend it. You’ll have enough to learn about from just using it as a server. You can learn about potential advantages of other distros later…
Gab vorher kein Firefox Maskottchen. Es gibt mehr oder weniger noch ein Mozilla Maskottchen mit dem ursprünglichen Dino-Logo, falls du das im Kopf hast:
It’s right-wing trolling that it’s specifically non-binary. It’s just iconography they use throughout Firefox, when displaying error messages or the like.
Okay, but just to be clear, the problem is not that it can’t do a timer. The problem is that it claims to be able to and even produces a result which looks plausible. It means, you cannot trust it to do anything that you can’t easily verify. If they could fix that overconfidence in a year, it would be much better.
Yeah, I can understand the frustration when an external decision forces you to disappoint some of your users, but ultimately you have to pick your battles. When neither the Python nor Rust ecosystem thinks those platforms are worth supporting, it’s probably not either worth it for you to worry…
It’s Apple’s programming language, kind of intended as a successor to Objective-C.
From what I hear, it’s actually decently designed and has quite a few similarities to Rust. Still not sure, how great it is outside of the Apple ecosystem…
My instance went down, so I’m way too late to make this joke, but anyways:
We’re not cantankerous, just a little …crabby. 🙃
Considering their policy for the majority of their existence has been that open-source is cancer, it might as well be viewed like that. Just buy the central open-source exchange platform and slowly make it worse to hurt all of open-source.
It’s key-based client authentication. Just open your SSH key’s .pub file in Microsoft Publisher, then export to PDF.
In my experience, the biggest problem is that maintainable code necessarily requires extending/adapting existing structures rather than just slapping a feature onto the side.
And if we’re not just talking boilerplate, then this necessarily requires understanding the existing logic, which problems it solves, and how you can mold it to continue to solve those problems, while also solving the new problem.
For that, you can’t just review the code afterwards. You have to do the understanding yourself.
And once you have a clear understanding, it’s likely that the actual code change is rather trivial. At least more trivial than trying to convey your precise understanding to an LLM/intern/etc…
I don’t think, we are doing different things. I create a new file, put
{}inside, then add it into theimports = [...];. 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?