Handle Bundler::HTTPError
s during bundle install
#3699
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In addition to
Bundler::Fetcher::NetworkDownError
s, a Bundler networking issue might be indicated by a variety ofBundler::HTTPError
s. By rescuing the parent error class, we can protect against any of these child errors from cluttering our telemetry.Implementation
I switched out the rescue for
Bundler::Fetcher::NetworkDownError
forBundler::HTTPError
.Automated Tests
I kept the original test and added a separate
Bundler::HTTPError
test, ensuring that this would catch both the parent error class and any of its children.