When inside a devcontainer I am unable to use any remote git commands (git pull, git fetch, …). The process does not seem to do anything, when executing git in the terminal there is no output at all and just (what seems like) busy waiting. I did not have this issue prior to today when the extension updated so I assume something broke with the update.
Steps to Reproduce
Open a devcontainer
Use git fetch / pull
Expected Behavior
Git should be able to fetch/pull data from a remote git provider
Hey @Polarising sorry for the inconvenience. We recently implemented GPG forwarding in our latest release and that might be causing the issue, the git command hangs if there’s not gpg agent running locally.
For me its still the same behavior on 1.0.32 as I had on 10.0.31
Using e.g. git pull will just do nothing (not even exit) - gotta manually stop the process from executing with ctrl + c in the terminal. I tried it on 10.0.30 again before to compare and it worked without any problems. So for me it’s not resolved yet
Any chance you can share the logs (output > dev container).
Also do you have GPG keys set on your local machine any chance ?
if so are you using GP4Win or the one that comes with git ?
Hey, first of all thank you for the fast response and no worries the rollback to old versions lets me work like I need to so don’t stress yourself for my sake! I am already very thankful all of you always respond so thoughtful and fast
Now to the topic:
Windows: No GPG tool is installed on my Windows system (gpg –version found no executable - I also never manually set anything related to GPG up).
WSL: While WSL does have a GPG tool installed, I have not configured any GPG keys there.
Git Configuration: Running git config --global gpg.program returns no value on both Windows and WSL.
Okay I got different behaviors on the two different machines I tried it on now. On my one machine yesterday it did not work and hang with 10.0.32 - on my other Machine it works with 10.0.32 without going into config and Disabling GPG Agent forwarding (It is active and works on 10.0.32) - I also reverted to 10.0.31 on this machine and that also worked with git. So it seems to be an error specific to my other setup.
Sadly I will not get to use that setup until next week again, but like I said there seem to be workarounds for me that work well. I will update you next week again.
Are you using the dev container inside WSL or just on windows with docker running there ?
Anyways, next time you get to do the flow please get me some logs via (inside container window) ctrl + shift + p > export logs > dev containers.
If it contains any sensitive data, just mail it to me on - [email protected]
The issue is, there are different protocols for unix based vs windows, so we have a custom implementation in place which is running into some edge case, and i can’t sleep at night till i get this thing fixed haha (jk)