Skip to content
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

"remote authentication required but no callback set" in pull after upgrading from 0.28 to 0.29 #2115

Open
FreeAndNil opened this issue Jul 30, 2024 · 1 comment

Comments

@FreeAndNil
Copy link

@bording we get the error "remote authentication required but no callback set" after upgrading from 0.28 to 0.29 when connecting to a company internal azure devops server.

This works great with the old version using windows authentication.

Reproduction steps

  • connect to a company internal azure devops server via windows authentication
      Signature signature = GetSignature();
      PullOptions pullOptions = new()
      {
        MergeOptions = new() { FileConflictStrategy = CheckoutFileConflictStrategy.Theirs }
      };
      MergeResult mergeResult = Commands.Pull(Repository, signature, pullOptions);

Expected behavior

Success

Actual behavior

LibGit2Sharp.LibGit2SharpException
HResult=0x80131500
Message=remote authentication required but no callback set
Source=LibGit2Sharp
StackTrace:
at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 154

Version of LibGit2Sharp (release number or SHA1)

0.29

Operating system(s) tested; .NET runtime tested

Windows 11, .NET 4.8

Seems to be related to #2065 and #2087

@mezzo1981
Copy link

Hi, any update on this ? we have the same issue...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants