Skip to content
This repository was archived by the owner on May 5, 2023. It is now read-only.

skip https.request patching if already done#25

Merged
TooTallNate merged 1 commit intoTooTallNate:masterfrom
vfernandestoptal:fix-https-request-patch-leak
Jun 5, 2019
Merged

skip https.request patching if already done#25
TooTallNate merged 1 commit intoTooTallNate:masterfrom
vfernandestoptal:fix-https-request-patch-leak

Conversation

@vfernandestoptal
Copy link
Copy Markdown
Contributor

Ran into the same issue as described in #22 when using PubNub JavaScript SDK, which includes this via superagent-proxy.

This fix prevents re-patching https method for each test executed by jest by checking for a marker to flag that the patch is already done.

fixes #22

@vfernandestoptal vfernandestoptal force-pushed the fix-https-request-patch-leak branch from 9c295a5 to f2aaaa3 Compare February 17, 2019 20:32
@vfernandestoptal vfernandestoptal changed the title skip http.request patching if already done skip https.request patching if already done Feb 17, 2019
@scotthovestadt
Copy link
Copy Markdown

This issue impacts many downstream libraries. Please consider accepting this PR.

jestjs/jest#8248

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

agent-base leaks memory when it is required

3 participants