The websocket client is closed, but messages are still being received.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
The websocket client is closed, but there are still messages being received. Our business wants the old messages to be discarded, but we have not found the code to clear the message queue. Is this a special scenario? Or in most scenarios, after the connection is closed, we still want the client to process the received messages.
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 websocket client’s close handling and the path that receives or queues messages; the issue does not name a file, test, or entry point. Determine the intended behavior after closure, then verify whether queued messages are discarded or still processed and add coverage for the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100