-
Notifications
You must be signed in to change notification settings - Fork 5k
[6.0.100-preview.4.21206.10][main branch] LibGit2Sharp System.NullReferenceException at git_diff_find_similar native method #50841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jkoritzinsky @AaronRobinsonMSFT @elinor-fung This issue happened after the issue #50410 was fixed. |
@jiangzeng01 Yes, we did observe this issue and I believe @jkoritzinsky has addressed that in our .NET 5 servicing and also recently put in a fix for .NET 6. |
See #50735. |
@AaronRobinsonMSFT Thanks! We will verify this with main branch builds. |
@AaronRobinsonMSFT This case is still failing today's latest SDK of main branch: dotnet-sdk-6.0.100-preview.4.21210.1. Could you please take a look? |
@jiangzeng01 Thanks. This will be investigated today. |
The latest SDK build from dotnet/installer is still using a runtime build from 7 days ago before the fix was merged. Once dotnet/installer takes an updated copy of dotnet/runtime, then the fix will be in a full sdk build. |
Specifically, this is blocked on dotnet/installer#10185, which is blocked on dotnet/sdk#16810. The dotnet/installer configuration requires the runtime to match the one the SDK was built with and dotnet/installer#10185 needs #51004, whose uptake into dotnet/sdk is part of dotnet/sdk#16810 |
@jkoritzinsky @AaronRobinsonMSFT Thanks for update, we will check after runtime build is updated in dotnet/installer. |
We were testing on Preview 3 builds last week, and now on main branch build. Do you think they are same issue with this ticket? @jkoritzinsky Error log example 1:
Error log example 2:
|
These look like the same issue to me. |
@jiangzeng01 Thank you for following up with these details. Understanding this sort of breadth of impact is key to how we think about making Interop code changes. @jkoritzinsky and @elinor-fung I think we should set aside some time to fill out our compat matrix. The above impact makes me think we are getting to point where we just don't touch the built-in system unless it is security related. |
I'm definitely feeling the same way. |
Verified with dotnet-sdk-6.0.100-preview.4.21215.11, affected cases passed. Close this ticket as fixed. |
Application Name: LibGit2Sharp (https://github.com/libgit2/libgit2sharp)
OS: Windows 10 RS5
CPU: X64
.NET Build Number: 6.0.100-preview.4.21206.10
Affected Application: git-istage global tool app (GlobalToolsNETCore21Part01)
https://github.com/terrajobst/git-istage
Verify Scenarios:
1). Windows 10 RS5 X64 + .NET Core SDK build 6.0.100-preview.4.21206.1 - main branch: Fail
2). Windows 10 RS5 X64 + .NET Core SDK build 6.0.100-preview.3.21202.5 - Preview 3 branch: Pass
3). Windows 10 RS5 X64 + .NET Core SDK build 5.0.104 : Pass
DevDiv bug: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1307298
Repro steps to run
<PackageReference Include="LibGit2Sharp" Version="0.26.2" />
Expected Result:
Should return the number of staged changes
Actual Result:
@dotnet-actwx-bot @dotnet/compat
The text was updated successfully, but these errors were encountered: