-
Notifications
You must be signed in to change notification settings - Fork 80
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
Daemon doesn't quit when sent SIGINT/SIGTERM #950
Comments
this might be related to some of the SSE stuff if we still have a connection open |
Yeah, removing keepAlive seems to stop this. I'll see if I can find a fix! |
I've opened a PR in SSE that I think will address this: It exposes a |
@grouma oops, my bad comment in that other PR caused this to close, but we still need changes here to call shutdown. |
Feel free to send a PR and I'll reopen.
…On Thu, Apr 23, 2020, 1:36 PM Danny Tuppeny ***@***.***> wrote:
@grouma <https://github.com/grouma> oops, my bad comment in that other PR
caused this to close, but we still need changes here to call shutdown.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#950 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOBNBN2QW2JUXFVXOK3273ROCRGRANCNFSM4MD5WTDA>
.
|
…ection This allows bypassing the keep-alive period and fixes dart-lang#950.
…ection This allows bypassing the keep-alive period and fixes dart-lang#950.
If I run a project with
pub global run webdev serve
and hit Ctrl+C (in my macOS terminal), it quits fine. However if I do the same forpub global run webdev daemon
, it doesn't quit. I think this worked in the past, as it's causing some of Dart-Code's integration tests to fail.Then I hit Ctrl+C and see:
However, it then continues to sit there and does not terminate (it does close the browser window though).
The app I'm testing with is here:
https://github.com/Dart-Code/Dart-Code/tree/master/src/test/test_projects/web/hello_world
I'm using a globally activated v2.5.6 of webdev.
The text was updated successfully, but these errors were encountered: