-
-
Notifications
You must be signed in to change notification settings - Fork 66
-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Can't stop a runaway query without killing the app #98
Comments
Thanks for reporting. Will take a look. |
The change introduces: - Throttles pushing script output messages to IPC client - Limits max number of script output messages to push to IPC client in a single script run - Script output messages will be cancelled when a script environment stops, effectively cancelling sending script output messages to IPC client - Optimizations in rendering output within SPA. Rendering is now debounced and pre-rendering work is more optimized
So this started me down a rabbit hole and finally had me focus on making some planned, and overdue, design changes to how script output is rendered. #112 introduces a number of changes and enhancements that include fixing this issue. It will go out with next release. It also, under the hood, lays down the foundation to introducing more |
Will keep open till new version is released |
Closing with publish of new v0.6.0 release. |
I'm unable to stop a runaway query without closing NetPad. It seems to only happen when logging to the console or using
.Dump()
.Minimal Repro
The text was updated successfully, but these errors were encountered: