1.
org/apache/lucene/facet/taxonomy/directory/DirectoryTaxonomyWriter.java
- Line 498: *Volatile not atomically updated*. Updating *nextID* based
on a stale value. Any intervening update in another thread is overwritten
2. org/apache/lucene/index/IndexReader.java
- Line 249: *Unguarded write*. missing_lock: Accessing *closed* without
holding lock *IndexReader.this*. Elsewhere,
"org.apache.lucene.index.IndexReader.closed" is accessed with
*IndexReader.this* held 2 out of 3 times.
3. org/apache/lucene/index/SnapshotDeletionPolicy.java
- Line 116: *Unguarded read*. missing_lock: Accessing *indexCommits* without
holding lock *SnapshotDeletionPolicy.this*. Elsewhere,
"org.apache.lucene.index.SnapshotDeletionPolicy.indexCommits" is accessed
with*SnapshotDeletionPolicy.this* held 4 out of 5 times.
- '*lastCommit*' accessed in both synchronized and unsynchronized
contexts.
4. org/apache/lucene/queries/function/valuesource/QueryValueSource.java
- Line 76 and 116: Passing *null pointer* *fcontext* to *createWeight*,
which dereferences it.
5. org/apache/lucene/index/SegmentInfos.java
- Line 687: Throwing *null exception* *exc*.
On Tue, Jul 14, 2015 at 10:59 AM, Rishabh Patel <
[email protected]> wrote:
>
> 1.
> org/apache/lucene/facet/taxonomy/directory/DirectoryTaxonomyWriter.java:
> 2.
>
>
> On Tue, Jul 14, 2015 at 10:44 AM, Dawid Weiss <[email protected]>
> wrote:
>
>> The 444 defects is an overwhelming number. Most of those automated
>> tools detect things that turn to be valid code (upon closer
>> inspection). Could you start by listing, say, the first 5 defects that
>> actually make sense and are indeed flawed code that should be fixed?
>>
>> Dawid
>>
>> On Tue, Jul 14, 2015 at 4:33 PM, Rishabh Patel
>> <[email protected]> wrote:
>> > Hello!
>> >
>> > I scanned the Lucene project with Coverity scanner. 444 defects have
>> been
>> > detected.
>> > Please check the attached report on the breakup of the issues. Some of
>> the
>> > issues are false positives.
>> >
>> > I would like to volunteer for fixing these defects.
>> >
>> > Before I start, could you please tell me whether I should I create a
>> single
>> > JIRA for a kind of issue (e.g. "Concurrent data access" or "Null pointer
>> > exception") or should multiple issues be created according to the
>> module of
>> > the files to be modified?
>> >
>> > --
>> > Sincerely,
>> > Rishabh Patel
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> --
> Sincerely,
> *Rishabh Patel*
>
>
>
--
Sincerely,
*Rishabh Patel*
