-
Notifications
You must be signed in to change notification settings - Fork 1.7k
VM: Implement Isolate.addErrorListener. #21188
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
Comments
This would also include Isolate.removeErrorListener. |
Marked this as blocking #21599. |
Added this to the 1.9 milestone. |
Set owner to @iposva-google. |
Marked this as blocking #22067. |
This comment was originally written by [email protected] Why the javascriptish name? Why not: isolate.onError.listen(handler); ? |
The "addErrorListener" is a low-level function, working directly on ports, so it's named for precision, not brevity. There is also a more high-level "Isolate.errors" stream that you can listen to. It's implemented in terms of addErrorListener. |
Are we still targeting 1.9 for this? |
r44307 Added Fixed label. |
Make it possible to receive uncaught errors from isolates by implementing Isolate.addErrorListener.
The text was updated successfully, but these errors were encountered: