Michael loves building software; he's been building search engines for
more than a decade, and has been working on Lucene as a committer, PMC
member and Apache member, for the past few years. He's co-author of
the recently published Lucene in Action, 2nd edition. In his spare
time Michael enjoys building his own computers, writing software to
control his house (mostly in Python), encoding videos and tinkering
with all sorts of other things. Michael is a DZone MVB and is not an employee of DZone and has posted 49 posts at DZone. You can read more from them at their website. View Full User Profile
Atlassian has opened up some doozy bugs over time, including one of the earliest bug numbers I've ever worked on, LUCENE-140. They sent me a t-shirt for fixing that one (thank you!).
imagine this: what if there were a sneaky bug in Lucene, say a certain
text fragment that causes an exception during indexing. A user opens an issue
to report this, including the problematic text fragment, yet, because
Jira uses Lucene, it hits an exception while indexing that fragment and
causes this one bug to be un-searchable and un-viewable when browsing!
An invisible bug fixed point.
It's somewhat mind bending to think
about, Lucene recursing on itself through Jira, yet it's theoretically
possible! Maybe we have a few of invisible bug fixed points lurking
already and nobody knows...