| ▲ | j16sdiz 16 hours ago |
| In TFA: I have so many bugs in the Linux kernel that I can’t
report because I haven’t validated them yet… I’m not going
to send [the Linux kernel maintainers] potential slop,
but this means I now have several hundred crashes that they
haven’t seen because I haven’t had time to check them.
—Nicholas Carlini, speaking at [un]prompted 2026
|
|
| ▲ | mtlynch 16 hours ago | parent | next [-] |
| Those aren't false positives; they're results he hasn't yet inspected. I wrote a longer reply here: https://news.ycombinator.com/item?id=47638062 |
| |
| ▲ | coldtea 13 hours ago | parent | next [-] | | >Those aren't false positives; they're results he hasn't yet inspected. It's not a XOR | | |
| ▲ | Ukv 12 hours ago | parent | next [-] | | The article quote was being given as the supposed source for "Claude Code also found one thousand false positive bugs, which developers spent three months to rule out", so should substantiate that claim - which it doesn't. If the claim was instead just "a good portion of the hundreds more potential bugs it found might be false positives", then sure. | |
| ▲ | tptacek 10 hours ago | parent | prev [-] | | Yes it is. They're not not false positives until they're reported and consume maintainer time. |
| |
| ▲ | bethekidyouwant 13 hours ago | parent | prev [-] | | some of them certainly are… |
|
|
| ▲ | sobiolite 12 hours ago | parent | prev [-] |
| The comment said "Claude Code also found one thousand false positive bugs, which developers spent three months to rule out.". Please explain how a bug can both be unvalidated, and also have undergone a three month process to determine it is a false positive? |