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.

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

curl error 6 while downloading https://repo.packagist.org/packages.json: Could not resolve host: repo.packagist.org #10716

Closed
mvorisek opened this issue Apr 7, 2022 · 4 comments
Labels
Milestone

Comments

@mvorisek
Copy link
Contributor

@mvorisek mvorisek commented Apr 7, 2022

see https://github.com/atk4/data/runs/5861526212?check_suite_focus=true#step:7:14

It seems on some status codes download is not retried.

@Seldaek Seldaek added this to the 2.2 milestone Apr 7, 2022
@Seldaek Seldaek added the Bug label Apr 7, 2022
@Seldaek Seldaek closed this as completed in 9bfd059 Apr 7, 2022
@mvorisek
Copy link
Contributor Author

@mvorisek mvorisek commented Apr 13, 2022

thanks, another issue with code 7 detected - https://github.com/atk4/ui/runs/6012531457?check_suite_focus=true#step:12:16 - but the code 7 is already added, does the retry really work?

@Seldaek
Copy link
Member

@Seldaek Seldaek commented Apr 14, 2022

The retry happens silently unless you have -vvv so probably it just failed several times and then it stops retrying.

@mvorisek
Copy link
Contributor Author

@mvorisek mvorisek commented Apr 14, 2022

Would it be possible to some delay between retries? It seems like webservers are not restarted atomically and retries /wo delay fail all. We run hundreds pipelines per hour and even a percentually small failures are a significant number per day.

Like 2nd retry /wo delay, 50 ms for 3rd retry, 100 ms for 4th retry, ... and retry by default at least 8x (eg. 50, 100, 200, 400, 800, 1600 ms = about 3 seconds in total)

@Seldaek
Copy link
Member

@Seldaek Seldaek commented Apr 29, 2022

@mvorisek done in da32264 although not with as many retries as this is I think a bit overkill, and we can't easily wait asynchronously - hopefully it helps tho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants