mafintosh / mafintosh/hyperlog
Swallowing "Not Found" errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 469
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I'm curious why this line is in the code:
https://github.com/mafintosh/hyperlog/blob/master/lib/replicate.js#L131
It caused me some serious headaches, I couldn't figure out why replication was failing. I actually still don't know why replication is failing cause I don't know _why_ I'm getting this error, but it was really tough tracking it down.
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 in lib/replicate.js at line 131 and trace how the “Not Found” error is handled during replication. Determine why the error is swallowed and what information is needed to diagnose replication failures. Done means the failure is no longer silently hidden and its cause can be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100