-
Notifications
You must be signed in to change notification settings - Fork 22
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
Timeout ignored on Node 12 #28
Comments
I'm actually experiencing an issue with v11.13.0 as well not respecting the timeout. |
maybe this would help |
I will create a fork to release this and more. In the meantime you can use patch-package and https://github.com/johncrisostomo/get-ssl-certificate/pull/27.patch |
How can this reproduced locally? |
The changes are available in get-ssl-certificate-next v3.0.0: |
@DanielRuf the link to the get-ssl-certificate-next repo does not work. Would you please share the correct link? Thank you! |
That was the correct link as of 2 years ago. It has since been taken down. Here's the npm package description: https://www.npmjs.com/package/get-ssl-certificate-next |
I confirmed https://www.npmjs.com/package/get-ssl-certificate-next has the fix implemented and it works. Thank you @DanielRuf ! |
I'm doing
let cert = await sslCertificate.get(host, 10000, port)
for a 10 second timeout, but it doesn't seem to be firing ever. If I hit a host that just hangs, this call hangs as well for 2 minutes. Should I put together a minimal repro example?I did notice that travis.yml only appears to go up to Node 11:
https://github.com/johncrisostomo/get-ssl-certificate/blob/master/.travis.yml
The text was updated successfully, but these errors were encountered: