-
Notifications
You must be signed in to change notification settings - Fork 578
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
fix(credential-provider-imds): destroy request handle on promise resolve/reject #2452
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2452 +/- ##
=======================================
Coverage ? 59.55%
=======================================
Files ? 493
Lines ? 26374
Branches ? 6265
=======================================
Hits ? 15708
Misses ? 10666
Partials ? 0 Continue to review full report at Codecov.
|
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 looks good to me, but needs to rebase.
/cc @trivikr |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Issue
#2451
Description
Issue in the
credential-provider-imds
package.Kills the dangling open request handle in
credential-provider-imds
after the promise resolves or rejects. If it is not killed manually we are relying on Node.js to clean it up which can take a long time or just simply never done. In my tests, a successful request remained open for 16 hours on a buildkite build. This causes issues especially with testing libraries like Jest which wait for all handles to be closed.Testing
How was this change tested?
Example Repo:
https://github.com/samchungy/jest-aws-sdk-v3-open-handle
Additional context
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.