JanusGraph / JanusGraph/janusgraph
calls to notify - should we keep track of the thread to call notify on?
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
Fortify low
1. [ConcurrentLRUCache](https://github.com/JanusGraph/janusgraph/blob/84ead7d/janusgraph-core/src/main/java/org/janusgraph/graphdb/util/ConcurrentLRUCache.java#L659)
2. [ConcurrentLRUCache](https://github.com/JanusGraph/janusgraph/blob/84ead7d/janusgraph-core/src/main/java/org/janusgraph/graphdb/util/ConcurrentLRUCache.java#L666)
Contributor guide
Research direction
Start by reviewing ConcurrentLRUCache.java at the two linked locations, lines 659 and 666, and trace the surrounding notify calls to understand the Fortify finding. Done means deciding whether the notifying thread must be tracked and documenting or implementing the resulting approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100