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
It looks like the library has no way to set custom network timeouts on capture and by default no timeouts are set by the underlying HTTP lib. In theory, it can lead to long (or even infinite?) pauses in case the sending is performed synchronously.
It looks like the library has no way to set custom network timeouts on
captureand by default no timeouts are set by the underlying HTTP lib. In theory, it can lead to long (or even infinite?) pauses in case the sending is performed synchronously.