You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
You can hardcode the previous value of 120000 if you want to preserve the behavior of previous Node.js versions (this value has been 120000 since it was introduced to Node.js, until the recent change).
I've been searching Github for codebases that rely on this timeout value and manually opening issues/PRs like this. My intent is to bring your attention to this subtle change and let you decide if it's necessary to address ❤️
The text was updated successfully, but these errors were encountered:
@jonchurch: thanks for the heads-up! We're going to hardcode it to 30s instead of 2m -- that's a better ceiling for our API calls -- so I'll do that in a new PR instead of merging yours, but appreciate your contribution.
Hey there, wanted to point out that under Node.js v13+ the default timeout has changed from 2 minutes to 0. This has the effect of never timing out.
In your current implementation, under Node.js v13, your requests will never timeout on the client side.
The change would need to be made here:
shippo-node-client/lib/shippo.js
Line 7 in b215c5a
You can hardcode the previous value of
120000
if you want to preserve the behavior of previous Node.js versions (this value has been120000
since it was introduced to Node.js, until the recent change).I opened #56 with the proposed change.
I've been searching Github for codebases that rely on this timeout value and manually opening issues/PRs like this. My intent is to bring your attention to this subtle change and let you decide if it's necessary to address ❤️
The text was updated successfully, but these errors were encountered: