Skip to content

bug: Client does NOT close properly (neither do server connections) #44

@john-bv

Description

@john-bv

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:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. 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):

  • commit: [7189861]
  • Version: 0.3.0-rc-5

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't workingCompleteThe code review for this issue has been completed; and is now being finalized.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions