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

Static interface type mismatch errors should be non-fatal #212

Open
anarthal opened this issue Feb 2, 2024 · 0 comments
Open

Static interface type mismatch errors should be non-fatal #212

anarthal opened this issue Feb 2, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@anarthal
Copy link
Collaborator

anarthal commented Feb 2, 2024

Currently, when the static interface finds a type mismatch, no more packets are read, thus making further operations impossible.

Rationale: a static interface type mismatch means that a serious error has occurred. Either the type definitions must be updated (which needs rebuilding) or the database definitions are out of sync (can be solved by closing and re-opening the connection, as in a network failure).

However, this causes surprises. Following the principle of least surprise, it would be good to make these errors non-fatal.

See #211

@anarthal anarthal added the enhancement New feature or request label Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant