tag:blogger.com,1999:blog-8623074010562846957.post9047309606636504278..comments2023-09-01T03:38:08.236-04:00Comments on Changing Bits: The invisible Lucene bug fixed pointMichael McCandlesshttp://www.blogger.com/profile/04277432937861334672noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8623074010562846957.post-6300181189267087962011-06-28T12:34:49.951-04:002011-06-28T12:34:49.951-04:00Reminiscent of Ken Thompson's C compiler backd...Reminiscent of Ken Thompson's C compiler backdoor described in 'Reflections on Trusting Trust' http://cm.bell-labs.com/who/ken/trust.html (but not on purpose in this case...).Glen Newtonhttps://www.blogger.com/profile/03639309432955855745noreply@blogger.comtag:blogger.com,1999:blog-8623074010562846957.post-8109635843237731302011-05-23T11:44:04.328-04:002011-05-23T11:44:04.328-04:00OK thanks Jed.OK thanks Jed.Michael McCandlesshttps://www.blogger.com/profile/04277432937861334672noreply@blogger.comtag:blogger.com,1999:blog-8623074010562846957.post-64290208739675626672011-05-22T19:03:30.413-04:002011-05-22T19:03:30.413-04:00While we haven't seen one with Lucene in parti...While we haven't seen one with Lucene in particular, the overall pattern has definitely been seen a few times. There was one very recently where we specifically had a reported case on our production server and somehow the bug regressed, bringing down our production server! Someone who didn't write a unit-test got found out that time…<br /><br />Also, within JIRA, not all views of an issue are sourced from the index (some are sourced from the DB). So if this theoretical situation did occur, you'd still be able to see the issue in some views.jedhttps://www.blogger.com/profile/03788339539345176707noreply@blogger.com