mafintosh / mafintosh/changes-feed
is lock/release necessary?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
doesn't levelup guarantee sequence of puts and callbacks?
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing the lock and release entry points in the changes-feed implementation, then check levelup's guarantees about the ordering of puts and callbacks. Determine whether those guarantees make the locking behavior redundant, and document the conclusion before proposing any change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100