Skip to content

Reconnect after unsafe response errors - #557

Draft
slabko wants to merge 1 commit into
masterfrom
invalidate-connection-on-exception
Draft

Reconnect after unsafe response errors#557
slabko wants to merge 1 commit into
masterfrom
invalidate-connection-on-exception

Conversation

@slabko

@slabko slabko commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • invalidate sockets after partial decoding, callback, timeout, and other unsafe response failures
  • reconnect lazily at the next client operation while preserving the original exception
  • preserve reusable connections after fully decoded server exceptions
  • add integration coverage for unsupported packets and types, callback failures, timeouts, compression, and native JSON serialization

Fixes #549

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

Successfully merging this pull request may close these issues.

Exceptions produced by the library leave the socket in inconsistent state

1 participant