"[Jul 14] Swapping the Case Unstuck a Backlog of Deferred Work"
I finally got the second GPU properly seated, and along the way found that two of the most important tickers had been missing from data for weeks This is the English version of a post originally written in Korean for my algorithmic trading system devlog (new tab). Today I finished the job I'd deferred a few days ago because of a case-fit issue, and along the way found a problem that had been…
On July 14, a developer resolved a backlog of deferred work by properly seating a second graphics card and addressing underlying data issues. The second GPU had initially been improperly seated, causing complications due to the power supply's mounting spot. Despite this, the developer managed to run a load test with both cards connected, finding them to be running stably with low temperatures.
While working on the GPU issue, the developer discovered that two of the most important stock tickers had been missing from their data for weeks. The name-extraction logic wasn't able to parse the [No info] format correctly, causing the two major tickers to have blank names. Although the raw data was already collected, this bug prevented the system from connecting those two important tickers with their news articles.
Additionally, the developer found that a collector sometimes skipped an entire day's worth of collection when it thought a page was blocked. This was due to a coincidental word match in an IT article, which triggered the block detection. The developer fixed this by allowing the page to be processed if it contained a normal-looking article list.
Another issue was discovered when requesting many tickers at once from an external API; some requests were silently failing. Reducing the concurrent request count eliminated these losses.
Finally, the developer adjusted the start time of the nightly automated analysis to after-hours trading to ensure cleaner data. They also switched the price reference point to the regular-session closing price instead of the after-hours price. With these changes, the developer was able to continue comparing a newly added model with the existing one, now that the data gaps were filled.
The developer emphasized the importance of checking not just whether totals are growing, but whether important tickers are getting covered evenly.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
