Comments (6)
lszomoru
commented on August 16, 2024
Could you please try the following steps to that we can take a closer look at the git auth flow:
- Close all instances of VS Code
- From a command prompt window run set GIT_TRACE=1 && code
- Open the integrated terminal and run git pull. You should see detailed logs related to SSH auth
- Click the "Sync Changes" button, or invoke the "Git: Pull" command.
- Open the https://code.visualstudio.com/docs/sourcecontrol/overview#_git-output-window and look at the logs.
from vscode.
Ross-Murphy
commented on August 16, 2024
Thanks for your response.
When performing the actions you requested I got the same results. The Sync action continues to spin and nothing times out. It just stops responding. No source control actions work after that. the indicator on the bottom left is spinning and source control icon on the left shows a "busy" clock.
The git output does not really provide anything in terms of errors.
I should note that when I was testing I noticed my git for windows old so I removed v2.37 and installed v2.45.1 and the results were the same.
git pull from the terminal in vscode works fine and asks for the passphrase of the key.
git output
2024-05-29 13:43:46.284 [info] Log level: Info
2024-05-29 13:43:46.284 [info] Validating found git in: "C:\Program Files\Git\cmd\git.exe"
2024-05-29 13:43:46.357 [info] Using git "2.45.1.windows.1" from "C:\Program Files\Git\cmd\git.exe"
2024-05-29 13:43:46.558 [info] > git rev-parse --show-toplevel [180ms]
2024-05-29 13:43:46.847 [info] > git rev-parse --git-dir --git-common-dir [108ms]
2024-05-29 13:43:46.873 [info] Open repository: c:\Operations\DEV\PowerShell-Deployments
2024-05-29 13:43:47.007 [info] > git config --get commit.template [120ms]
2024-05-29 13:43:47.024 [info] > git rev-parse --show-toplevel [120ms]
2024-05-29 13:43:47.052 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/dev-test refs/remotes/dev-test [122ms]
2024-05-29 13:43:47.147 [info] > git rev-parse --show-toplevel [115ms]
2024-05-29 13:43:47.195 [info] > git status -z -uall [122ms]
2024-05-29 13:43:47.273 [info] > git rev-parse --show-toplevel [119ms]
2024-05-29 13:43:47.333 [info] > git merge-base refs/heads/dev-test refs/remotes/origin/dev-test [129ms]
2024-05-29 13:43:47.354 [info] > git config --get commit.template [126ms]
2024-05-29 13:43:47.402 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/dev-test refs/remotes/dev-test [130ms]
2024-05-29 13:43:47.448 [info] > git rev-parse --show-toplevel [163ms]
2024-05-29 13:43:47.475 [info] > git -c core.longpaths=true rev-list --count --left-right refs/heads/dev-test...refs/remotes/origin/dev-test [132ms]
2024-05-29 13:43:47.535 [info] > git status -z -uall [124ms]
2024-05-29 13:43:47.539 [info] > git check-ignore -v -z --stdin [117ms]
2024-05-29 13:43:47.562 [info] > git rev-parse --show-toplevel [102ms]
2024-05-29 13:43:47.601 [info] > git diff --name-status -z --diff-filter=ADMR c76a1b03e752c08732f36d8582dd275c38ef168b...refs/remotes/origin/dev-test [116ms]
2024-05-29 13:43:47.685 [info] > git rev-parse --show-toplevel [118ms]
2024-05-29 13:43:47.786 [info] > git rev-parse --show-toplevel [93ms]
2024-05-29 13:43:47.930 [info] > git rev-parse --show-toplevel [137ms]
2024-05-29 13:43:48.035 [info] > git show --textconv :Ansible/InventoryGen.ps1 [95ms]
2024-05-29 13:43:48.036 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [86ms]
2024-05-29 13:43:48.372 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [129ms]
2024-05-29 13:43:48.461 [info] > git show --textconv :Ansible/InventoryGen.ps1 [78ms]
2024-05-29 13:44:06.765 [info] > git log --oneline --cherry dev-test...dev-test@{upstream} -- [70ms]
2024-05-29 13:44:08.129 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [62ms]
2024-05-29 13:44:08.202 [info] > git show --textconv :Ansible/InventoryGen.ps1 [67ms]
2024-05-29 13:45:40.111 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [59ms]
2024-05-29 13:45:40.176 [info] > git show --textconv :Ansible/InventoryGen.ps1 [60ms]
2024-05-29 13:45:43.146 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [59ms]
2024-05-29 13:45:43.211 [info] > git show --textconv :Ansible/InventoryGen.ps1 [60ms]
2024-05-29 13:45:58.804 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [64ms]
2024-05-29 13:45:58.871 [info] > git show --textconv :Ansible/InventoryGen.ps1 [61ms]
2024-05-29 13:46:02.314 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [62ms]
2024-05-29 13:46:02.378 [info] > git show --textconv :Ansible/InventoryGen.ps1 [59ms]
2024-05-29 13:46:05.252 [info] > git ls-files --stage -- C:\Operations\DEV\PowerShell-Deployments\Ansible\InventoryGen.ps1 [59ms]
2024-05-29 13:46:05.315 [info] > git show --textconv :Ansible/InventoryGen.ps1 [58ms]
from vscode.
Ross-Murphy
commented on August 16, 2024
I should also note that this happens both in VSCode local and VSCode when connected to WSL.
Also the Vscode GitHub output shows the following
024-05-29 13:55:21.709 [info] Log level: Info
2024-05-29 13:55:22.719 [warning] Failed to update repository branch protection: No GitHub authentication session available.
from vscode.
lszomoru
commented on August 16, 2024
@Ross-Murphy, thanks for getting back to me on this. I would like us to concentrate on the local scenario first and then look at WSL. Did you start VS Code using set GIT_TRACE=1 && code from the command prompt? I am asking as the git output log does not seem to contain the GIT_TRACE logs. Are they being shown when you perform a git action from the integrated terminal?
from vscode.
Ross-Murphy
commented on August 16, 2024
@lszomoru I'm sorry I don't know what happened there. I had done so but seems like I pasted the wrong info. Sigh... users.
VSCode Git Output
2024-05-30 11:04:36.142 [info] Log level: Info
2024-05-30 11:04:36.142 [info] Validating found git in: "C:\Program Files\Git\cmd\git.exe"
2024-05-30 11:04:36.206 [info] Using git "2.45.1.windows.1" from "C:\Program Files\Git\cmd\git.exe"
2024-05-30 11:04:36.398 [info] > git rev-parse --show-toplevel [172ms]
2024-05-30 11:04:36.398 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:36.670 [info] > git rev-parse --git-dir --git-common-dir [103ms]
2024-05-30 11:04:36.671 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:36.695 [info] Open repository: c:\Operations\DEV\PowerShell-Deployments
2024-05-30 11:04:36.845 [info] > git config --get commit.template [130ms]
2024-05-30 11:04:36.845 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:36.854 [info] > git rev-parse --show-toplevel [129ms]
2024-05-30 11:04:36.854 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:36.879 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/dev-test refs/remotes/dev-test [131ms]
2024-05-30 11:04:36.880 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:36.981 [info] > git rev-parse --show-toplevel [119ms]
2024-05-30 11:04:36.981 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.016 [info] > git status -z -uall [124ms]
2024-05-30 11:04:37.106 [info] > git rev-parse --show-toplevel [117ms]
2024-05-30 11:04:37.106 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.140 [info] > git merge-base refs/heads/dev-test refs/remotes/origin/dev-test [113ms]
2024-05-30 11:04:37.140 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.164 [info] > git config --get commit.template [119ms]
2024-05-30 11:04:37.164 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.180 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/dev-test refs/remotes/dev-test [124ms]
2024-05-30 11:04:37.180 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.224 [info] > git rev-parse --show-toplevel [109ms]
2024-05-30 11:04:37.224 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.278 [info] > git -c core.longpaths=true rev-list --count --left-right refs/heads/dev-test...refs/remotes/origin/dev-test [126ms]
2024-05-30 11:04:37.278 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.301 [info] > git status -z -uall [113ms]
2024-05-30 11:04:37.337 [info] > git rev-parse --show-toplevel [102ms]
2024-05-30 11:04:37.337 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.388 [info] > git diff --name-status -z --diff-filter=ADMR c76a1b03e752c08732f36d8582dd275c38ef168b...refs/remotes/origin/dev-test [99ms]
2024-05-30 11:04:37.388 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.396 [info] > git check-ignore -v -z --stdin [118ms]
2024-05-30 11:04:37.444 [info] > git rev-parse --show-toplevel [96ms]
2024-05-30 11:04:37.444 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:37.538 [info] > git rev-parse --show-toplevel [87ms]
2024-05-30 11:04:37.538 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:04:39.793 [info] > git log --oneline --cherry dev-test...dev-test@{upstream} -- [63ms]
2024-05-30 11:04:39.793 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
From the integrated terminal
C:\Operations\DEV\PowerShell-Deployments> git pull
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
Enter passphrase for key 'C:\Users\rmurphy/.ssh/id_rsa':
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
Already up to date.
Git Output when I remove the passphrase from the key
2024-05-30 11:10:35.789 [info] > git log --oneline --cherry dev-test...dev-test@{upstream} -- [82ms]
2024-05-30 11:10:35.789 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:10:37.411 [info] > git pull --tags origin dev-test [1615ms]
2024-05-30 11:10:37.411 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
From github.com:Ross-Murphy/PowerShell-Deployments
* branch dev-test -> FETCH_HEAD
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:10:37.483 [info] > git config --get commit.template [66ms]
2024-05-30 11:10:37.483 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:10:37.489 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/dev-test refs/remotes/dev-test [66ms]
2024-05-30 11:10:37.490 [info] warning: unknown trace value for 'GIT_TRACE': 1
If you want to trace into a file, then please set GIT_TRACE
to an absolute pathname (starting with /)
2024-05-30 11:10:37.558 [info] > git status -z -uall [64ms]
from vscode.
lszomoru
commented on August 16, 2024
@Ross-Murphy, sorry for not getting back to you on this until now. I just looked at the logs and it seems that 1 is not a valid value for the GIT_TRACE environment variable. Sigh. Could you please gather the logs after you start VS Code using set GIT_TRACE=true && code. Sorry about that!
from vscode.
Related Issues (20)
- ★35+ Free PlayStation Gift Cards~FREE PSN GIFT CARD CODES 2024 Free PSN Codes 2024 ✅✅
- ❥FREE PSN Codes June 2024❥FREE PSN Gift Card Codes 2024: Free Playstation Gift Cards
- ׂ╰┈➤FREE XBOX GIFT CARD CODES 2024 UNUSED-THE BEST GAMES ON XBOX
- ツGift Cards Available |[No Survey] Xbox Code Generator 2024 Without HuMaN Verificationツ
- [+10000 ROBUX HACKS]✅☄️Free Roblox Gift Card Codes 2024| Free Robux Promo Codes 2024 Unused✅☄️
- 💸Unlimited Nintendo Gift Card Generator 💸 Free Nintendo Gift Card Codes 💸 Free Nintendo Eshop Cards 2024
- 💷[2025-2024]💷Psn Gift Card Codes 2024 ✼ Free Psn Code Generator $100 PlayStation Store Gift Card🗳️
- NEW***!!99999+ Coin master free spins and coin links generator 2024
- (((EASY WAY)) Get Spins & Coins in Coin Master iOS/Android Tutorial - Coin Master Free Spins 2024🔥
- Today's Get +99999 Free Spins In Coin Master (iOS & Android)-Coin Master Free Spins 2024
- Daily Updated]]!!~Coin Master Spins & Coins Free 2024 | Coin Master free spins and coins links (June 2024)
- GlitchⒶ 2024👌How To Get Free Money On Cash App in 2024>>Free Cash App Money The Simple Trick & Win
- $99.99 rOBUX cODE ✿HOW TO rEDEEM gIFT cODES FOR rOBLOX - rOBLOX gUIDE -2024✿
- [[June 27, 2024]]⚡Unused FREE Roblox Gift Card Codes^@^Roblox Promo Codes for 2024 |
- ╰┈➤FREE XBOX GIFT CARD CODES 2024 UNUSED-THE BEST GAMES ON XBOX⚡
- ☄️*100%☄️ WORKING ✔︎[[FREE!!]]✔︎BINGO BLITZ FREE CREDITS 2024 - FREEBIES PROMO CODES REWARDS
- 💚💚OMG💶⋆GET~LATEST!!^ FREE PAYPAL Gift Card Codes Generator No Human Verification 2024 [ HWSy]💚
- 💷{{FREE {💷}}CASH APP MONEY FREE GENERATOR 2024 NEW CODE [Center_Naws_Tool]
- ⇢Nintendo eShop Switch Gift Card Codes 2024 ✼ Free Nintendo eShop Switch Code Generator
- Nintendo eShop Switch Codes — Nintendo eShop Switch Gift Card Codes Free 2024
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode.