[Signalr-Cpp-Client] Cannot close connection if connection state is connecting (deadlock for ~30 secs)
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 290
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the bug
When I call Stop() after Start(), and if the internet is slow or the server cannot be connected somehow, the app will be in deadlock for around 30 secs. (which I assume, is the timeout period)
### Expected Behavior
If connection is cancelled after Start() has been processing, Signalr should cancel and stop trying to reach the server immediately instead of waiting for timeout.
### Steps To Reproduce
- call Start() on hub_connection
- make the server cannot connect and keep in connecting state
- call Stop() on hub_connection
### Exceptions (if any)
_No response_
### .NET Version
_No response_
### Anything else?
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.