Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing event dispatch when a client disconnects unexpectedly #72

Closed
yallie opened this issue Nov 21, 2024 · 0 comments
Closed

Failing event dispatch when a client disconnects unexpectedly #72

yallie opened this issue Nov 21, 2024 · 0 comments

Comments

@yallie
Copy link
Collaborator

yallie commented Nov 21, 2024

Describe the bug
When serving multiple clients with connected events and MessageEncryption enabled, server fails to dispatch new events if one of the clients disconnects unexpectedly (network error, process crash, etc).

Originates in this discussion: #62

To Reproduce
Steps to reproduce the behavior:

  • Start a server and two clients
  • Connect both clients to the server and subscribe to its events
  • Fire an event and get it handled on both clients
  • Disconnect the first client
  • Fire an event and get an error
  • Note that if MessageEncryption == false, everything works seamlessly

Expected behavior

  • Server should handle disconnected clients gracefully.
  • Clients shouldn't depend on one another.
  • Server behavior shouldn't be dependent on MessageEncryption setting.

Additional notes
The issue seems to be related to the closed RsaKeyPair safe handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant