Workaround/fix for libgit2sharp custom marshal type cast failure #216
Conversation
This file contains 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
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.
It seems that although we were always consistently loading libgit2sharp in our own load context (as we do with all assemblies we can find in our directory), the CLR fails in its p/invoke custom marshaler unless we've loaded it in the default load context -- as if someone else loaded it in the Default context and somehow we were using one context to create the
FilePathobject and the other to cast it toFilePath. That doesn't seem to be the case here, but at least loading it in the default context works around what may be a bug (https://github.com/dotnet/coreclr/issues/19654).Fixes #215