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

interrupt ocap #2736

Open
gordonwoodhull opened this issue Jun 16, 2020 · 1 comment
Open

interrupt ocap #2736

gordonwoodhull opened this issue Jun 16, 2020 · 1 comment

Comments

@gordonwoodhull
Copy link
Contributor

If there is a bug in a JS ocap and it doesn't call its continuation, this can hang the cell and RCloud UI completely.

When we do an interrupt with the Stop button, could we also detect if we're blocked by an async call to JS, and if so, issue an error with whatever info we have about the ocap?

Sure, this might leave the front-end in a bad state, but it seems like it should still be responsive.

@gordonwoodhull
Copy link
Contributor Author

gordonwoodhull commented Jun 25, 2020

In particular, the Run All button is helpful because it starts a new session and will reload any packages which have been rebuilt. This makes it possible to debug multiple iterations on a package without reloading the page.

But if a continuation was dropped, then Play All is not available.

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

No branches or pull requests

1 participant