IsAlive not accurate
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
When using this websocket library as a client only it seems that .IsAlive() does return false all the time even though a connection is established. I had a look in the code, it should definetly work...
Any idea/help would be appreciated!
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 locating the IsAlive() implementation and the client connection-state handling. Reproduce the behavior with a client-only connection and inspect how an established connection is represented. Done means IsAlive() accurately reports the state for an established client connection, with a regression test if the project has coverage for this behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100