This time it's because the glossary package not actually generating an actual glossary. No errors. The one warning is some straight nonsense. Oh, and the build time is still absurd for a quick toy to make sure that the glossary package does what I want.
I have a great respect for what (La)TeX did at the time of its release. And it's still the least worse option for scientific papers, notes, etc., but to call this an ergonomic tool is delusional.
Can't wait to see the ratio of useful answers to reply guy nonsense of people defending LaTeX's build times because it's a macro expansion language as though that a) excuses it from being even remotely performant or b) its somehow a revelation to me at this point.
Wait wait wait, according to tex.stackexchange.com/questiโฆ there's a four commands I need to run to generate a glossary? jfc, I am not doing this to myself am I?
Can you guess what happens when you increase the amount of cash-on-hand poor workers have?
...
...
...
They become more productive and make fewer mistakes.
"Alleviating financial concerns allows workers to be more attentive and productive at work."
nber.org/papers/w28338
What is the point of AWS Codepipeline having a stop feature if it doesn't stop anything and runs to the complete timeout period but instead of saying waiting it says stopping?
So the Lambda that is running into an error a) posts its call stack in JSON and b) doesn't include the line from my code that is invoking it. This must be what hell looks like.