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

proxy: raise UpstreamRegistryError if we can't request upstream #1220

Merged
merged 1 commit into from
Mar 31, 2022

Conversation

flavianmissi
Copy link
Contributor

requests will either throw a RequestException or a ConnectionError if it
fails to request the given url for whatever reason.
callers are only expected to treat UpstreamRegistryError, so we throw it
instead of the requests related exceptions, adding the original message
to the new exception.

requests will either throw a RequestException or a ConnectionError if it
fails to request the given url for whatever reason.
callers are only expected to treat UpstreamRegistryError, so we throw it
instead of the requests related exceptions, adding the original message
to the new exception.
@flavianmissi flavianmissi merged commit b941a03 into quay:master Mar 31, 2022
@flavianmissi flavianmissi deleted the proxy-cache-errors branch March 31, 2022 13:28
Sunandadadi pushed a commit to Sunandadadi/quay that referenced this pull request Mar 31, 2022
…#1220)

requests will either throw a RequestException or a ConnectionError if it
fails to request the given url for whatever reason.
callers are only expected to treat UpstreamRegistryError, so we throw it
instead of the requests related exceptions, adding the original message
to the new exception.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants