Improve handling of peerbook down
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This is mainly for testing, peerbook has a slower boot, so when webexec boots & tries to
connect sometimes, there no peerbook and the agent exits.
webexec should retry connecting to peerbook if there's a failure.
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 webexec's startup path where it connects to peerbook. Reproduce the case where peerbook boots slowly, then verify that a failed initial connection is retried and webexec remains running until peerbook is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100