GCM get/store in WSL takes several minutes during standard git operations (git pull/push)

[JPNels]

When i git pull/push, i see a delay of sometimes 5+ minutes. Turning on GIT_TRACE and GCM_TRACE i see it is stuck in "git-credential-manager get" call

I am using git in WSL linked to my windows GCM as specified here - https://learn.microsoft.com/en-us/windows/wsl/tutorials/wsl-git#git-credential-manager-setup

I have updated to latest git & gcm

[mjcheetham]

Hello! Thanks for reporting this, and enabling tracing.

However, in order to have GCM_TRACE be passed through to the Windows host from WSL you need to also set the following environment variable:

WSLENV=$WSLENV:GCM_TRACE

So, for example:

WSLENV=$WSLENV:GCM_TRACE GCM_TRACE=1 GIT_TRACE=1 git pull

In the past I have noticed issues with the WSL <-> Windows interop, specifically in the network/DNS resolution, where it would hang for a long time. Can you verify that git-credential-manager.exe diagnose works correctly when run from the WSL session?

[mjcheetham]

Closing due to lack of response. If this issue reoccurs please feel free to reopen this issue, or open a new one. Please make sure to include trace information so that we can help.

[JPNels]

@mjcheetham sorry for the delay. With those logs enabled. i see where the get command is taking longest, this step takes about 2.5 min every time

18:21:30.891701 ...pClientFactory.cs:80 trace: [CreateClient] Git's SSL/TLS backend is: OpenSsl
18:23:04.375977 ...ClientFactory.cs:113 trace: [CreateClient] Custom certificate verification has been enabled with certificate bundle at C:/Program Files/Git/mingw64/etc/ssl/certs/ca-bundle.crt
18:23:52.687536 ...sHostProvider.cs:332 trace: [GetAzureAccessTokenAsync] Acquired Azure access token. Account=<REDACTED>' Token='********'
18:23:52.703242 ...GitCommandBase.cs:53 trace: [ExecuteAsync] End 'get' command...