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

fix: Treat 502s and 503s as transient for GCS OS #2202

Merged
merged 2 commits into from
Jun 11, 2024
Merged

fix: Treat 502s and 503s as transient for GCS OS #2202

merged 2 commits into from
Jun 11, 2024

Commits on Jun 11, 2024

  1. fix: Treat 502s and 503s as transient for GCS OS 

    A refactoring introduced lately caused multiple restarts in provers
(namely BWGs) when GCS was unavailable (502 or 503). This is a sporadic,
once in a while, but still invalides tens of minutes of work and makes
proving fickle and slow. This PR addresses the issue and restores old
behavior pre-refactoring.
    @EmilLuta
    EmilLuta committed Jun 11, 2024
    Configuration menu
    Copy the full SHA
    2f07eb6 View commit details
    Browse the repository at this point in the history

  2. Update prover Cargo.lock

    @EmilLuta
    EmilLuta committed Jun 11, 2024
    Configuration menu
    Copy the full SHA
    7cdcec6 View commit details
    Browse the repository at this point in the history