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

fix: correct docker-pull retry logic #296

Merged
merged 2 commits into from
Jan 24, 2025
Merged

fix: correct docker-pull retry logic #296

merged 2 commits into from
Jan 24, 2025

Conversation

pbrisbin
Copy link
Member

@pbrisbin pbrisbin commented Jan 24, 2025

This was originally written against exceptions, but we're calling a
process and using the exit code to throw later, so it was never raising
any exceptions at the point of our retry logic. Instead we should move
it outside and use the non-exception retrying based on that exit code.

This was originally written against exceptions, but we're calling a
process and using the exit code to throw later, so it was never raising
any exceptions at the point of our retry logic. Instead we should move
it outside and use the non-exception `retrying` based on that exit code.
It's currently failing. It was also never needed here anyway, we only
need to check that on CI.
@pbrisbin pbrisbin enabled auto-merge (rebase) January 24, 2025 14:39
@pbrisbin pbrisbin changed the title pb/next fix: correct docker-pull retry logic Jan 24, 2025
@pbrisbin pbrisbin merged commit 1b10129 into main Jan 24, 2025
6 checks passed
@pbrisbin pbrisbin deleted the pb/next branch January 24, 2025 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant