Coding 2021-09-19
Come work on MOTR! We have: inscrutable errors!
Come work on MOTR! We have: inscrutable errors!
Doing code archeology to figure out how obscure the bugs I was hitting were.
This post was delayed thanks to: something in my Neovim install or environment that jacked up the file recovery process somehow.
It's kind of hard to read the output from the nameless-actions version of MOTR, but, like, oh well.
I have no idea what flit build was doing when I had uncommitted work, but I extremely did not like it, and it makes me wonder if I can trust flit build output in general during development. (Maybe it was because I wasn't bothering to pass --wheel, so it was making the wheel from the sdist instead of directly? Eugh.)
"I cannot think of any problems with this. [shortly thereafter] I have found a problem."
This does involve a bunch more I/O than the noxfile, but I don't think it's a perceptible difference.
A stripped-down, simple core, surrounded by a dozen layers of weird adaptors...
"That simplifies things in a complicated way."
At some point I should come up with a system for archiving or culling old runs, if I'm going to be shoving this much stuff in the folders...