Keep connection alive?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 748
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone,
I notice that writing data to hyperdb that is connected to remote peers (using discovery-swarm) seems to be taking a very long time and most of time will even fail if the node has been sitting idle for a long time.
Is there a way to keep the connection alive? It's still showing there are peers connected tho.
Thanks!
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
No source files, tests, or entry points are named. Start by reproducing a write to a hyperdb connected to remote peers through discovery-swarm after the node has been idle, then inspect the connection and write paths to determine whether the failure is reproducible and what behavior should count as fixed.
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
- 20/100