Describe the bug
The Client and Connection structs both have an issue when communicating with eachother, that being, when the tasks are paused, there is no way to "wake them up" currently, meaning if a disconnect signal is received by the server, the other tasks will have no way of knowing that this signal was received causing a weird case where the connection freezes and has to wait for the connection timeout.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
These structs should dispatch signals properly to all tasks without any need for locking.
Screenshots
If applicable, add screenshots to help explain your problem.
Server versions (please complete the following information):
Describe the bug The
Client
andConnection
structs both have an issue when communicating with eachother, that being, when the tasks are paused, there is no way to "wake them up" currently, meaning if a disconnect signal is received by the server, the other tasks will have no way of knowing that this signal was received causing a weird case where the connection freezes and has to wait for the connection timeout.To Reproduce Steps to reproduce the behavior:
Expected behavior These structs should dispatch signals properly to all tasks without any need for locking.
Screenshots If applicable, add screenshots to help explain your problem.
Server versions (please complete the following information):