-
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
feat: add signal option to Deno.resolveDns #17384
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems resource associated with AbortController
is not cleaned up if the API finishes successfully
@bartlomieju you are right; this seems to be a problem for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, requires conflict resolution.
# Conflicts: # ext/net/01_net.js # runtime/js/40_read_file.js # runtime/js/40_write_file.js
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few unrelated test duplications left over. Do we have a unit test file for DNS APIs where the AbortSignal usage could be tested for leakage like the readFile functions?
no; unsure how we could add it as the DNS API has its whole own thing. i'll open an issue to add such a test for now. |
Closes #14406