-
Notifications
You must be signed in to change notification settings - Fork 49
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
Possibly leaked handle? #129
Comments
I am also facing the same issue. Is there any update? |
Had a similar problem with Jest so I wrote a library called sync-request-curl. The usage is the same. sync-request-curl is free from this bug and has better performances from leveraging node-libcurl, but doesn't have close to the same level of compatibility as sync-request. It only works with recent versions of NodeJS and has no support for JavaScript in the Browser. I believe this issue is also closely linked with #137. The cause is sync-rpc and is explained in issue 10: |
* Bump azure-pipelines-task-lib to fix open handles - microsoft/azure-pipelines-task-lib#932 - ForbesLindesay/sync-request#129 * Fix "Could not locate the bindings file" * Run mock tasks asynchronously
* Bump azure-pipelines-task-lib to fix open handles - microsoft/azure-pipelines-task-lib#932 - ForbesLindesay/sync-request#129 * Fix "Could not locate the bindings file" * Run mock tasks asynchronously * [dep] Remove superfluous libraries * Try node 10 entrypoint * Revert "Try node 10 entrypoint" This reverts commit b962ed3.
* Bump azure-pipelines-task-lib to fix open handles - microsoft/azure-pipelines-task-lib#932 - ForbesLindesay/sync-request#129 * Fix "Could not locate the bindings file" * Run mock tasks asynchronously * [test] Download Node.js only once
Running tests using sync-request and Jest has Jest detecting a possibly leaked handle.
The text was updated successfully, but these errors were encountered: