This bug was potentially introduced by revisions 224 and 226. We should have reviewed more carefully, since these don't seem to be proper fixes.
This bug was potentially introduced by revisions 224 and 226. We should have reviewed more carefully, since these don't seem to be proper fixes.