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
I think it's pretty much always a good idea to have a default timeout on I/O; it prevents some catastrophic behavior in production that there's really no good reason to allow. Most libraries do this, like the Apache client which clj-http wraps, which defaults to the system timeout: https://stackoverflow.com/questions/9734384/default-timeout-for-httpcomponent-client
Apparently the new Java API which this wraps doesn't set a default timeout, which I think is unfortunate. Would you consider adding one to this library?
The text was updated successfully, but these errors were encountered:
The request doesn’t sound unreasonable. Would you like to open a PR for it? I’ll leave this issue open for the time being in case there are any immediate objections by anyone.
I think it's pretty much always a good idea to have a default timeout on I/O; it prevents some catastrophic behavior in production that there's really no good reason to allow. Most libraries do this, like the Apache client which clj-http wraps, which defaults to the system timeout: https://stackoverflow.com/questions/9734384/default-timeout-for-httpcomponent-client
Apparently the new Java API which this wraps doesn't set a default timeout, which I think is unfortunate. Would you consider adding one to this library?
The text was updated successfully, but these errors were encountered: