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

corro-client: handle deserialization error correctly #246

Merged
merged 1 commit into from
Jul 30, 2024

Conversation

pborzenkov
Copy link
Contributor

Change ID still needs to be incremented even if the entry is not valid.

Change ID still needs to be updated even if the event fails to deserialize
@pborzenkov
Copy link
Contributor Author

@jeromegn I've decided to deserialize as before and only fallback to non-typed QueryEvent in case deserialization fails, so we only pay the double deserialization price in these rare cases.

@pborzenkov pborzenkov merged commit 8f8e552 into main Jul 30, 2024
4 checks passed
@pborzenkov pborzenkov deleted the handle-deser-error branch July 30, 2024 12:44
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.

2 participants