Do not use LibGit2SharpException
overload for unknown message
#2163
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.
Background
The
LibGit2SharpException
class has a constructor overload that takes two parameters and attempts to callString.Format
to convert the values into a single string.Unfortunately if the provided message contains text between curly braces then the string.format throws an exception.
Related PR OctopusDeploy#10
Result
Since this message could have any value, it seems risky to assume that the provided string will have a
{0}
that will accept theGitErrorCategory
as a replacement value. In fact it seems rather unlikely that this would typically apply at all. As a result this handler would ignore the error category in the best case, or throw an exception in the worst case.Alternative
I'd also be happy to ignore the category entirely since its likely that it is of type
GitErrorCategory.Unknown
anywayAlternative snippet