Add a customized GitRepositoryError and funnel all Git operations through a method that throws one of those if an operation fails. #2958
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ough a method that throws one of those if the operation fails. This makes sure that Git failures clients can distinguish from other Process errors (so failure handling can be customized), and that they all have a location.
abertelrud
requested review from
aciidgh,
friedbunny and
neonichu
as code owners
|
@swift-ci please smoke test |
|
Looks like the CI is currently having unrelated issues: |
|
The macOS test failure seems to be because of not using a new enough |
|
@Swift-C please smoke test |
|
@swift-ci please smoke test |
|
The Linux failures seem to have been due to the SwiftDriver CMake problem. Trying again. |
|
@swift-ci please smoke test |
neonichu
approved these changes
Oct 7, 2020
|
@swift-ci please smoke test |
|
The test failures are different this time but still completely unrelated to this PR: |
|
The test failure is the same as in #2970 |
|
@swift-ci please smoke test |
abertelrud
deleted the
eng/throw-a-specific-error-for-any-git-operation-failure
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This makes sure that Git failures clients can distinguish from other Process errors (so failure handling can be customized), and that they all have a location. At present the location for an error during a cloning operation is the remote URL, while the operation for an operation on a local clone is the path of the local clone. We might want to extend this in the future so that local clones also keep track of the URL, but this will require the GitRepository to keep a copy of the associated RepositorySpecifier of its origin remote. This would in turn require a change to the Repository protocol so that all methods take a RepositorySpecificier, and it would require changes to all the clients. So that should be a separate PR.