-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Deno.serve: request.signal is aborted even though the response finished successfully #27005
Comments
cc @littledivy |
This has been intended behavior ever since request abort signals were introduced in |
I just updated the example, please check again the oddness of this design. |
`serve()` was removed in Deno v1 (May 2020). Release notes: https://github.com/denoland/deno/releases/v1.0.0 Related: #17 Note: the `abort` signal listener was removed because it is always triggered, even when the response is successfully sent See also: denoland/deno#27005
Seems weird to me that signal.aborted is supposed to mean successfully completed. I think we should change this. |
Version: Deno 2.1.1
Example:
Prints:
This is awkward, and may even lead to potential bugs.
Bun doesn't seem to have this problem.
The text was updated successfully, but these errors were encountered: