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
Yes. The fetcher is a very simple implementation and assumes a lot of conditions. We should create an exception upon timeout and convert it into a validation error somehow. Do you have any better ideas?
In my implementation of a custom URLFetcher I use a unirest instance with timeout. But this is hardly a good idea for a library - additional dependency will complicate implementation
@this is good enough. I just want the users to know that the default implementation is simple and works for normal scenarios; however, it doesn't handle all possible exceptions. There is a way to substitute with customized implementations. I will write a document for this. Thanks.
Looks like the URLFetcher has a default values (infinite) for a connection/socket timeout. Right?
The text was updated successfully, but these errors were encountered: