You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also experiencing this. I get a vscode notification in the bottom right saying Chaining cycle detected for promise #<Promise>
I'm on macOS Monterey 12.3 with vs code 1.65.2 and GitLens v12.0.5, git version 2.32.0 (Apple Git-132)
Refreshing the window fixes the issue, it seems. I suspect it might have something to do with my repo structure. It contains a (gitignored) symlink to a folder on an SMB volume, which happened to be unmounted when i encountered the error this time (not sure about in the past). I have now correctly added it to my login items, so i'll see if this pops up when i boot my computer tomorrow, when the SMB share should be loaded.
It's interesting to note that the issue went away by refreshing the window, even before i'd mounted the SMB share.
@mattklein123 Do you have any symlinks in your repository too?
Can both of you please enable debug logging by running from GitLens: Enable Debug Logging from the Command Palette (F1 or ctrl/cmd+shift+p). This will enable logging to the GitLens and GitLens (Git) channel in the Output pane.
Once enabled, please reproduce the issue, and attach the log from the both GitLens and GitLens (Git) channels.
I encountered this again today. My editor had two files open, call them File A and File B
GitLens output: https://pastebin.com/e9WEp3ys (I've censored the filename from this log, but it's referring to the file i was viewing, which was File A) GitLens (Git) output:
(GitLens (Git) output only showed up after i closed File A, which brought focus to File B for the first time in the session)
The error notification popped up multiple times without ever writing anything to GitLens (Git). Here's what theGit output shows (sometimes, but not always, it seems) when this happens:
I've installed v2022.4.2705 and not ran into the issue so far, at least. Annoyingly, i never found a reliable repro, so i can't be 100% certain the fix worked, but if it doesn't happen in the next few days it's probably fine
Activity
eivind-hovedkvarteret commentedon Mar 30, 2022
Also experiencing this. I get a vscode notification in the bottom right saying
Chaining cycle detected for promise #<Promise>I'm on macOS Monterey 12.3 with vs code 1.65.2 and GitLens v12.0.5,
git version 2.32.0 (Apple Git-132)Refreshing the window fixes the issue, it seems. I suspect it might have something to do with my repo structure. It contains a (gitignored) symlink to a folder on an SMB volume, which happened to be unmounted when i encountered the error this time (not sure about in the past). I have now correctly added it to my login items, so i'll see if this pops up when i boot my computer tomorrow, when the SMB share should be loaded.
It's interesting to note that the issue went away by refreshing the window, even before i'd mounted the SMB share.
eamodio commentedon Mar 31, 2022
@mattklein123 Do you have any symlinks in your repository too?
Can both of you please enable debug logging by running from GitLens: Enable Debug Logging from the Command Palette (F1 or ctrl/cmd+shift+p). This will enable logging to the GitLens and GitLens (Git) channel in the Output pane.
Once enabled, please reproduce the issue, and attach the log from the both GitLens and GitLens (Git) channels.
Thank you!
mattklein123 commentedon Mar 31, 2022
Probably yes. I will try to get you more logs.
eivind-hovedkvarteret commentedon Apr 5, 2022
I encountered this again today. My editor had two files open, call them File A and File B
GitLensoutput: https://pastebin.com/e9WEp3ys (I've censored the filename from this log, but it's referring to the file i was viewing, which was File A)GitLens (Git)output:(
GitLens (Git)output only showed up after i closed File A, which brought focus to File B for the first time in the session)The error notification popped up multiple times without ever writing anything to
GitLens (Git). Here's what theGitoutput shows (sometimes, but not always, it seems) when this happens:eamodio commentedon Apr 13, 2022
Can you try to see if the issue is still reproducible in the GitLens insiders edition?
You can install the GitLens insiders edition from here.
Please be sure to disable or uninstall the stable version of GitLens first.
artemisSystem commentedon Apr 23, 2022
Just ran into this as well, on gitlens insiders
v2022.4.1302Here's my GitLens debug output:
5 remaining items
eamodio commentedon Apr 27, 2022
Sorry for the delay on this one -- took me a bit to track down.
Can you please verify this fix in tomorrow's GitLens insiders edition?
You can install the GitLens insiders edition from here.
Please be sure to disable or uninstall the stable version of GitLens first.
eivind-hovedkvarteret commentedon Apr 27, 2022
I've installed v2022.4.2705 and not ran into the issue so far, at least. Annoyingly, i never found a reliable repro, so i can't be 100% certain the fix worked, but if it doesn't happen in the next few days it's probably fine
Fixes #1936 promise cycle when validating access
github-actions commentedon Jun 24, 2022
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.