hub-client: emit diagnostics when websockets fail
Open
Nobody has claimed this yet.
enhancement
quarto-hub
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
We need better diagnostics for websocket connection issues, like Gordon is experiencing right now.
Contributor guide
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 locating the hub-client websocket connection and failure-handling entry points in the repository. Reproduce a websocket connection failure and trace what diagnostics are currently available; done means useful diagnostics are emitted for websocket connection issues, with coverage added where the existing test structure supports it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100