Handle exceptions and null returns from CredentialsProvider. #1239
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.
Add exception handling and null checking around the call to the
CredentialsProvider
callback andGitCredentialHandler
method. Without these, exceptions will cross the boundary into C code, which I believe is bad.I got here because I want to supply a
CredentialsProvider
that only applies to certain hosts, and this provides a way to return an error code to libgit2 when I have no credentials to provide.Pull request #1130 would add a null check here, but not other exception handling. It would translate null to
GitErrorCode.Error
, while I'm proposing to translate it toGitErrorCode.PassThrough
so that a null credentials object behaves like a null credentials provider.