Missing nodes causing trouble!
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 748
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
In cabal, the group somehow got synced a feed that has some missing nodes. I suspect that a number of key lookups are going through that missing node, causing hyperdb to stall out waiting for that node to arrive. This seems to have the effect that even certain old data is also now inaccessible: I think the prefix trie has to traverse the missing node in order to get to that older data. As a result, only a subset of the hyperdb is available through `get`.
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 reproducing the missing-node synchronization scenario described for cabal, then trace how hyperdb's prefix trie handles get lookups when an intermediate node is unavailable. Confirm whether older data is blocked by the missing node. Done means get can still access unaffected older data, or the issue is narrowed to a specific lookup path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100