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
If osc can resolve a remote service with an ipv6 address, but the ipv6 endpoint is not accessible (fails to connect), osc hangs for large periods at a time. The timeout for each connection is in minutes rather than seconds.
This means on a host with ipv6, that for some reason fails to connect to https://api.opensuse.org, each connection takes 60 - 120 seconds to fail, causing osc to take forever to achieve anything.
osc should have a faster timeout for connection failures. I'm sure 5 seconds would be reasonable. Or at least something configurable.
The text was updated successfully, but these errors were encountered:
Osc has 3 retries by default with backoff factor 2.
That means it usually fails in about 12 seconds.
Are you sure the endpoint is not really accessible?
Isn't the connection only extremely slow?
If the connection gets established and data is flowing (even at a minimal rate), the timeout doesn't trigger, I think.
If osc can resolve a remote service with an ipv6 address, but the ipv6 endpoint is not accessible (fails to connect), osc hangs for large periods at a time. The timeout for each connection is in minutes rather than seconds.
This means on a host with ipv6, that for some reason fails to connect to https://api.opensuse.org, each connection takes 60 - 120 seconds to fail, causing osc to take forever to achieve anything.
osc should have a faster timeout for connection failures. I'm sure 5 seconds would be reasonable. Or at least something configurable.
The text was updated successfully, but these errors were encountered: