Skip to content

Broken repositories view #1936

Closed
Closed

Description

@mattklein123

I'm seeing the following error pop up and also show in the GitLens debug output:

TypeError: Chaining cycle detected for promise #<Promise>

None of the repositories in the repository view will expand correctly, though they do show up.

GitLens version: 12.0.5
Git version: 2.32.0

Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-10T15:36:26.048Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.13.0-39-generic

Example log output:

[2022-03-29 21:30:04.505] [  244] Repository(/home/mklein/Source/infra).access — failed • 2 ms
TypeError: Chaining cycle detected for promise #<Promise>

Let me know how I can help debug. Thank you!

Activity

  1. eivind-hovedkvarteret commented on Mar 30, 2022

    @eivind-hovedkvarteret

    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.

  2. eamodio commented on Mar 31, 2022

    @eamodio
    Member

    @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!

  3. added
    needs-more-infoNeeds further information, steps, details, etc.
    and removed
    triageNeeds to be looked at
    on Mar 31, 2022
  4. mattklein123 commented on Mar 31, 2022

    @mattklein123
    Author

    @mattklein123 Do you have any symlinks in your repository too?

    Probably yes. I will try to get you more logs.

  5. eivind-hovedkvarteret commented on Apr 5, 2022

    @eivind-hovedkvarteret

    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:

    [2022-04-05 09:41:18.148] [      6ms] [/Users/eivind/Documents/munki/munki-repo] git ls-files -- <File B>
    

    (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:

    [2022-04-05T09:49:02.718Z] > git fetch --all [586ms]
    [2022-04-05T09:49:02.743Z] > git symbolic-ref --short HEAD [6ms]
    [2022-04-05T09:49:02.748Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/production refs/remotes/production [5ms]
    [2022-04-05T09:49:02.754Z] > git remote --verbose [5ms]
    [2022-04-05T09:49:02.754Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [5ms]
    [2022-04-05T09:49:02.759Z] > git config --get commit.template [4ms]
    [2022-04-05T09:49:03.812Z] > git symbolic-ref --short HEAD [6ms]
    [2022-04-05T09:49:03.818Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/production refs/remotes/production [6ms]
    [2022-04-05T09:49:03.824Z] > git remote --verbose [5ms]
    [2022-04-05T09:49:03.824Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [6ms]
    [2022-04-05T09:49:03.830Z] > git config --get commit.template [5ms]
    [2022-04-05T09:49:03.900Z] > git ls-files --stage -- /Users/eivind/Documents/munki/munki-repo/<file> [6ms]
    [2022-04-05T09:49:03.906Z] > git cat-file -s a522cab77b0b7237bbb183e0efd11b4fe0134e65 [5ms]
    
  6. added
    triageNeeds to be looked at
    and removed
    needs-more-infoNeeds further information, steps, details, etc.
    on Apr 13, 2022
  7. eamodio commented on Apr 13, 2022

    @eamodio
    Member

    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.

  8. artemisSystem commented on Apr 23, 2022

    @artemisSystem

    Just ran into this as well, on gitlens insiders v2022.4.1302

    Here's my GitLens debug output:

    [2022-04-23 11:44:40.153] [  14c] RepositoryNode(gitlens:repository(<my repository>)).ensureSubscription
    [2022-04-23 11:44:40.153] [  14c] RepositoryNode(gitlens:repository(<my repository>)).ensureSubscription completed • 0 ms
    [2022-04-23 11:44:40.157] [  14d] RepositoryNode(gitlens:repository(<my repository>)).ensureSubscription
    [2022-04-23 11:44:40.157] [  14d] RepositoryNode(gitlens:repository(<my repository>)).ensureSubscription completed • 0 ms
    [2022-04-23 11:44:40.157] [  14e] GitProviderService.getRemotesWithProviders — s=<my repository>
    [2022-04-23 11:44:40.157] [  14f] GitProviderService.getRepository — s=<my repository>
    [2022-04-23 11:44:40.157] [  14f] GitProviderService.getRepository returned <my repository> • 0 ms
    [2022-04-23 11:44:40.157] [  150] GitProviderService.getRemotesWithProviders — s=<my repository>
    [2022-04-23 11:44:40.157] [  151] GitProviderService.getRepository — s=<my repository>
    [2022-04-23 11:44:40.157] [  151] GitProviderService.getRepository returned <my repository> • 0 ms
    [2022-04-23 11:44:40.157] [  152] Repository(<my repository>).access — ue=worktrees
    [2022-04-23 11:44:40.157] [  14e] GitProviderService.getRemotesWithProviders completed • 0 ms
    [2022-04-23 11:44:40.157] [  150] GitProviderService.getRemotesWithProviders completed • 0 ms
    [2022-04-23 11:44:40.157] [  152] Repository(<my repository>).access — failed • 0 ms
    TypeError: Chaining cycle detected for promise #<Promise>
    
  9. self-assigned this
    on Apr 27, 2022
  10. 5 remaining items

  11. eamodio commented on Apr 27, 2022

    @eamodio
    Member

    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.

  12. eivind-hovedkvarteret commented on Apr 27, 2022

    @eivind-hovedkvarteret

    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

  13. modified the milestones: , June 2022 on May 16, 2022
  14. modified the milestones: June 2022, 12.0.7 on May 25, 2022
  15. added a commit that references this issue on May 25, 2022
    fc9d4f4
  16. added and removed
    pending-releaseResolved but not yet released to the stable edition
    on May 25, 2022
  17. github-actions commented on Jun 24, 2022

    @github-actions

    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.

  18. locked as resolved and limited conversation to collaborators on Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions