A exception handling with backoff for when connection to trickle server fails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
When I restart the Orchestrator the trickle connections spam `ConnectionRefusedError` tracebacks.
Suggest we add a exception catch and backoff for this. Also just close the subscribers/publishers if off for say 30 seconds?
May be better to close immediately or within 5 seconds though.
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 the Orchestrator restart path and the subscriber/publisher connection handling that produces ConnectionRefusedError. Reproduce the traceback while the trickle server is unavailable, then determine the agreed backoff and closure timing; done means failures no longer spam tracebacks and disconnected subscribers/publishers are handled as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100