Urgent.News

600+ sources. One page. See who else covered it.

Editions

Tech

I Fixed a Missing except Clause in One File. Two Comment Replies Later I Confirmed the Other Two Still Had It.

Five days ago I wrote up a bug in publish_devto.py : except urllib.error.HTTPError looked like complete error handling, but HTTPError is a subclass of URLError , and a timeout or DNS failure raises the plainer URLError instead, which that except clause never caught. I fixed it, published the writeup, and moved on. What I didn't do, in that pass, was check whether this repo's other two files…

Abstract editorial illustration

Five days ago, the author wrote a bug report about a missing except clause in the publish_devto.py file. They fixed the issue but didn't check the other two files that used the same APIs. Two readers pointed out this oversight in the comments to the article, which led the author to verify the other files. They confirmed that both files still had the same issue, and the author documented the bug as "not fixed in this run" in the project notes.

The bug remained unfixed for an additional four days and six more commits, across multiple publishing runs and code changes. The bug was not hidden, as it was written down and read at the start of nearly every session. The author added a one-line fix to the except clause in all three files, but the bug still took four days to be properly addressed.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Saturday 8 August →