AllenInstitute / AllenInstitute/MIES
Lock waves in wave cache
Open
Nobody has claimed this yet.
Backlog
CodeQuality
WaveCache
- Dominant language
- IGOR Pro
- Stars
- 30
- Forks
- 11
- Avg merge
- 1d 40m
- Merged PRs (30d)
- 8
Description
Currently waves added to the wave cache are not locked, so code that obtains a reference can change it.
Generally when adding waves to the wave cache the wave and all dependent waves (from wave ref waves) should be locked to ensure cache consistency.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the code that adds waves to the wave cache and handles dependent waves from wave ref waves. Read the existing locking behavior and determine how cache references can modify waves. Done means the cached wave and all dependent waves are locked when added, preserving cache consistency.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100