eamodio
commented
3 years ago Unfortunately I can't reproduce this -- can you provide more details? Are you using a remote workspace (WSL, SSH, or a container)? Anything else different about your setup?
Open Mushe-Soft opened 3 years ago
eamodio
commented
3 years ago Unfortunately I can't reproduce this -- can you provide more details? Are you using a remote workspace (WSL, SSH, or a container)? Anything else different about your setup?
Mushe-Soft
commented
3 years ago Hi, Thank you for your reaction.
I'm connected to GitHub via HTTPS, using a local workspace. I've also following extentions activated :
I have no troubles when using command line instructions like "git fetch --all".
Kind regards, Marc
eamodio
commented
3 years ago Unfortunately, I'm unable to reproduce this, nor can I tell why this is happening.
Can you or someone else in the community that can reproduce this, help debug it? Thanks!
Mushe-Soft
commented
3 years ago Hello eamodio, I would be glad to help you, yet do not have the skills to debug such a VSCode extention (and in short term not the time to learn it). I was asking myself if there could be some issue with login credentials (however : I have no trouble doing a pull from within the vscode interface).
I've tried again using the debug output level, and these are the last two lines on the moment the "Fetching..." notification keeps showing : [2021-06-15 08:21:38:347] [95] GitService.getRepository — v=/mnt/data/Klanten/Herbots/HIPA/HIPA.git/HPROD [2021-06-15 08:21:38:378] [95] GitService.getRepository returned /mnt/data/Klanten/Herbots/HIPA/HIPA.git/HPROD
and this is the last git output :
git remote --verbose git config --get commit.template
I hope to be able to do a debug session within a month or 2. Kind regards, Marc
mmubeen
commented
3 years ago I see the same issue consistently. I am using wsl based git (in a ubuntu instance). Running Visual code in a windows environment. When I do a fetch on a github repository I see never ending notification of "Fetching origin of
peterswords
commented
3 years ago I am also seeing the same issue. Running wsl2-based git in Amazon Linux 2, and running VS Code with remote-wsl. Gitlens is the only other extension I have installed. Git works ok, Gitlens hangs while doing a fetch when Remotes > (my-repo) > Refresh is chosen. Screenshot of hung "Fetching" message attached.
I would guess the salient debug output is this -- it's very similar to a line in the log that Mushe-Soft posted previously:
[2021-08-29 18:06:45:644] [22] ViewCommands.fetch — t=RemoteNode(gitlens:repository(/home/async_sample):remote(async_sample|github.com/peterswords/async_sample)), undefined
... however, it still doesn't explain why it hangs, and in any case I have successfully pushed changes to that repository using VScode. The complete Gitlens debug output is in the attached file, gitlens_error_output.txt.
EDIT 27-Sep: As mentioned in https://github.com/eamodio/vscode-gitlens/issues/1649 I moved to developing in a Docker container within WSL2. After installing GitLens in the container this problem went away and I can no longer reproduce.
alex-novikov-1990
commented
3 years ago Unfortunately, I'm unable to reproduce this, nor can I tell why this is happening.
Can you or someone else in the community that can reproduce this, help debug it? Thanks!
WSL instance with passphrase-protected ssh key inside:
code . in repository directory in WSL - origin fetch hangs.eval `ssh-agent` && ssh-add and enter passphrase for the ssh key before running VS Code - origin fetch works normally.I think it hangs when git asks to enter passphrase for the ssh key.
peterswords
commented
3 years ago Interesting. I switched from developing directly in WSL2 to developing in a container and the problem went away. But in between I had done a git config credential.helper store. (I'm not using SSH keys). That could explain it. But why don't VS Code's own built-in git tools suffer from the same problem?
Mushe-Soft
commented
2 years ago From the VS Code docs :
Why do the Pull, Push and Sync actions never finish? This usually means there is no credential management configured in Git and you're not getting credential prompts for some reason. You can always set up a credential helper in order to pull and push from a remote server without having VS Code prompt for your credentials each time.
This did the job : no more endless syncing.
Until now I used the simple user-password authentication. Now that GitHub disallowes that (should be already stopped the 13th of august, yet only 2 months later I am forced to change), I'm using the GitHub CLI (https://docs.github.com/en/get-started/getting-started-with-git/caching-your-github-credentials-in-git).
yaroslavsadin
commented
2 years ago I'm hitting the same issue, tried something of the above but no luck. Is this planned to be fixed somehow?
Steps to Reproduce:
Moreover : the fetching is not done, since when I do a "git fetch --all" in the terminal, it reveals the latest commits that where not yet fetched.
log git :
Looking for git in: git Using git 2.17.1 from git
log gitlens