Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Check if it makes sense to retry on non-http network errors #96

Open
arthuraraujo-msft opened this issue Feb 29, 2024 · 0 comments
Open

Check if it makes sense to retry on non-http network errors #96

arthuraraujo-msft opened this issue Feb 29, 2024 · 0 comments
Labels
investigation A task that needs further investigation
Milestone
Future

Comments

@arthuraraujo-msft
Copy link
Contributor 

          Not really, there was no requirement to retry on non-http errors.

Looking at the curl list of possible errors, it looks like the one that could happen would be the host resolution error. I can check if Winget currently retries on another of their existing flows, but that would be a different requirement from this.

Originally posted by @arthuraraujo-msft in #90 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
investigation A task that needs further investigation
Projects
None yet
Milestone
Future
Development

No branches or pull requests
1 participant
@arthuraraujo-msft