We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The specification is currently silent on implementation behavior when state notification callbacks raise an exception.
I suggest that we define that exceptions are ignored (but SHOULD be logged). It is the responsibility of the application to make sure the cb is safe.
SHOULD
The text was updated successfully, but these errors were encountered:
Yes, I think an implementation note encouraging implementations to ignore but loudly log CB exceptions is a good idea.
Sorry, something went wrong.
andre-merzky
No branches or pull requests
The specification is currently silent on implementation behavior when state notification callbacks raise an exception.
I suggest that we define that exceptions are ignored (but
SHOULD
be logged). It is the responsibility of the application to make sure the cb is safe.The text was updated successfully, but these errors were encountered: