db with non-synchronized feed never emits ready
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 748
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
I have a database which never emits ready when loaded. It seems to feel one of the streams is longer than it actually has the head for, and heads never returns waiting for the content.
My storage folder with secret key removed is at dat://47708c6ca35eb967992db5299ea1a3f9ac11e13dce19acfa7beeecf329bd3d24
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 load using the provided storage folder and dat URL, with the secret key removed as noted. Trace the non-synchronized feed while loading, especially the heads lookup and ready event, to identify why it waits for content. Done means the database emits ready reliably for this case and the regression is covered by a reproducible test.
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
- 25/100