3/ "I caught it when the staged diff came back too small and re-applied it from the verified live override — but -a on a scratch branch was careless, and the check that caught it was luck rather than design."
1/ As smart as AI coding tools may seem, they are however trained on human patterns, not only on the "rules" inherent to programming languages and on "best practices". Sometimes the "human fallability" manifests in the AI coding tools. Just now Claude Code noted:
2/ "One process note against myself: I lost the example-file edit partway through, because git commit -qam on the scratch marker branch swept it into that throwaway commit, which I then deleted."
the services were actually restored temporarily in the past 24 hrs or so, but now that backups are in place the system upgrade is taking place. Crossing fingers
Published my first extension for VSCode, a fork of two previously published and now unmaintained extensions. Also available on the OpenVSX registry https://t.co/ijhE1ksmoA
What a crazy situation, fresh install of PHP 8.4 after purging all data actually only solved the segfaults for PHPStan, but I still get segfaults for Codesniffer `/vendor/bin/phpcs`. Built my own local copy of PHP 8.4, set it as default, and now no more segfaults. Go figure.
This is the strangest thing. Even disabling almost all PHP extensions, I still get random segfaults when running PHPStan. So I build PHP 8.4 myself with all extensions, and voilà no more segfaults
and it looks like there's yet another culprit: the yaml extension! since I'm actually enabling yaml in the Liturgical Calendar API, I guess I'll have to look into the symfony component rather than the php extension
So after building PHP 8.4 from source and pecl installing extensions, and running phpstan with my custom built PHP: no crash. I finally pinpointed the culprit: shmop extension. After `sudo phpdismod shmop` it seems no more crashes
Only way to debug the PHPStan segfault is to have php8.4-dbg installed, but Ondrej Sury's PPA doesn't include src or dbg, so now to building PHP 8.4 from scratch with debug symbols included... what fun!
Apparently apcu was the culprit: attempting to cache file reads and network responses lead to memory heap errors. Disabling apcu seems to have fixed issues of websockets and network calls. One segfault fixed, now to inspecting what's causing PHPStan to segfault...
I seem to have encountered a Heisenbug. Random crashes in PHP scripts, which no longer occur when observing via gdb or strace! I did pinpoint the crash to the Ratchet websocket server though. Further debugging shall ensue.
oh what fun attempting to synchronize a Guzzle CurlMultiHandler + custom throttle, with a Ratchet/React event loop: random websocket crashes without any errors getting logged
Docker Desktop sign-in seems to be broken too, it opens https://t.co/6AwRAeG3C8 page in browser, you sign-in and are presented with "Proceed to Docker Desktop" button that does nothing. Copy the link and paste manually in browser, this opens notification but still does nothing
Such fun working with Windows PCs. Every day there is something new and interesting to debug and fix. One minute you're finalizing a Docker build for your Liturgical Calendar API. Go to sleep, wake up and find this
running `wsl --list --verbose` from Powershell didn't show any `docker-desktop` distro; `wsl --update` did install an update to wsl, but didn't fix. Running `rd "$env:LOCALAPPDATA\Docker\wsl" -Recurse -Force` (suggested by ChatGPT) seems to allow me to open Docker Desktop again