A matter of opinion, but I actually don’t think the current headline is too bad. When I saw the headline and “github.com/anthropic” next to it, my initial assumption was that it must be a problem introduced by Claude Code rather than a bug in bash or something.
That said, I don’t think your edited headline was bad either, but perhaps there wasn’t enough reason not to use the original (which is a default I personally appreciate on HN).
First, HN prefers the source title unless that title is misleaing clickbait.
Second, the problem is not consistently off-by-one errors, as there is a manifestation shown in the bug of an off-by-much-less-than-one error. The problem looks like a "for some reason it seems to be roundtripping numbers in text through a numeric representation which has about [perhaps exactly] the same precisions issues as float64" issue.
Comments
Why did Hacker News rename the title of this post? It was originally: "Claude Code Introduces Off-by-One Errors"
Original: https://pasteboard.co/xTjaRmnkhRRo.png
Unilaterally Edited: https://pasteboard.co/rDPINchmufIF.png
Looks like mods changed the title to the title of the GitHub Issue. This from HN guidelines is probably why:
Good catch on the guidelines. But that github issue title obviously misses the point. The whole point is that it's a silent error in Claude Code.
A matter of opinion, but I actually don’t think the current headline is too bad. When I saw the headline and “github.com/anthropic” next to it, my initial assumption was that it must be a problem introduced by Claude Code rather than a bug in bash or something.
That said, I don’t think your edited headline was bad either, but perhaps there wasn’t enough reason not to use the original (which is a default I personally appreciate on HN).
Probably for a couple reasons:
First, HN prefers the source title unless that title is misleaing clickbait.
Second, the problem is not consistently off-by-one errors, as there is a manifestation shown in the bug of an off-by-much-less-than-one error. The problem looks like a "for some reason it seems to be roundtripping numbers in text through a numeric representation which has about [perhaps exactly] the same precisions issues as float64" issue.