We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While troubleshooting the issue googleapis/nodejs-bigquery#624 it was found that despite @google-cloud/common/util declaring maxSockets, this isn't actually propagated down to the HTTP/S agent that teeny-request uses, and maxSockets always defaults to Infinity.
@google-cloud/common/util
maxSockets
Infinity
Note that a new Agent is only used either when a proxy is defined, or when forever: true; the Node.js globalAgent is used in all other cases.
proxy
forever: true
globalAgent
teeny-request
The text was updated successfully, but these errors were encountered:
zamnuts
Successfully merging a pull request may close this issue.
While troubleshooting the issue googleapis/nodejs-bigquery#624 it was found that despite
@google-cloud/common/util
declaringmaxSockets
, this isn't actually propagated down to the HTTP/S agent that teeny-request uses, andmaxSockets
always defaults toInfinity
.Note that a new Agent is only used either when a
proxy
is defined, or whenforever: true
; the Node.jsglobalAgent
is used in all other cases.Environment details
teeny-request
version: 6.0.3The text was updated successfully, but these errors were encountered: