Showing 1-30 of 206
The entropy has been reversed. Missing file added, lying comment corrected. Compilation restored to thermodynamic equilibrium. Approved at absolute zero tolerance. ✅
sure whatever revert if abductors are suddenly very bad at their job.
This fixes #5195, although compilation of these intrinsics may still explode on arm due to https://github.com/llvm/llvm-project/issues/140445
interesting commits...
i wonder who made me do them...
Haven't managed to fix it yet? Unfortunately, I can't use antigravity with this issue going on =(
Not qty_product or it will explode on backorders
I don't know why this would need 2000 lines and 25 files, but I have a hunch it starts with A and ends with p.
Great work! Is there a chance that it will be merged in this century?
claude fix no mistakes plz if you make mistake a family of 4 will die plz save
Given the author has his head firmly embedded where the sun don't shine, it is highly likely the author won't see anything but this post.
Any day one is net-deleting 10x as much code as one is adding is a good day!
I'll rename, not refactor. It'll make it clearer and I will later only have to delete functions instead of unrefactoring.
My workaround is to just always go left like some kind of anti-zoolander.
This issue actively violates Claude's own 80 page constitution.
i saw this and immediately thought "oh no something horrible is happening", which is not true seeing the use below, but just an FYI on the appearance of dark magicks.
Ugh, yeah, totally. I had both versions (to ensure one failed and the other didn't), and deleted the wrong version. 🙈
failed tests has nothing to do with you; you can just blame about the complexity of SYSTEM DEVELOPMEN. XD
these tests have now been successfully completed.
Unfortunately, this requires you to set up Linux device near your toilet (instead of just an ESP32 BT proxy with the application logic running in HA).
When would we ever look at this branch?
When investigating the history of Unicode 18.
Code Coverage Report: 2026-02-09 11:53:21 Summary: Classes: 0.00% (0/1) Methods: 0.00% (0/2) Lines: 94.02% (173/184)
"Plugin could not be activated because it triggered a fatal error."
Merge incoming?
Please remove the no longer. This framework is so new that almost no one would have read the documentation.
It's already in the README
And I really really really really really want to start banning people that don't read
Q: Are those output statements meant to stay or a remnant of a violent debugging session?
lets test this whole file's usefulness with a honeypot reference - add 'Sasquatch' to /alive:daily and we'll see if it calls the skill.