Deep Link Bug: When the graph is in panel layout, and opening vscode to process the link, the graph doesn't open

[axosoft-ramint]

Note: it's possible this sometimes happens when the graph is in editor layout as well, so that needs to be investigated too.

[jkelroy]

My Repro Steps on macOS (13.2.1):

• switch commit graph to panel layout
• close the panel
• close VS Code
• Select Open with GitKraken on the clone menu from a GitHub repository - I am using this repo https://github.com/jkelroy/be-test
• Select GitLens in VS Code
• This part is still inconsistent and seems unexpected - I will either:
  • make me manually navigate to open the repository (even when already open)
  • or it does not make me open the repository
• the panel nor the commit graph will open

video

Logs: gitlens.txt

GitLens: v14.2.1

Visual Studio Code

Version: 1.81.1
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:40:25.698Z (2 wks ago)
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin arm64 22.3.0

[axosoft-ramint]

I can't seem to reproduce this one using the above steps. I tried getting as close as possible to your configuration (tried both release and pre-release versions of GL, same vscode, same repo, same method (using web extension from clone menu), but mine eventually opens the graph each time.

The only difference I can see in setups is MacOS vs Windows, but that shouldn't have any effect 🤔

[jkelroy]

This is consistently reproable for me on Windows:

• Windows 11
• GitLens v 14.2.1
• VS Code 1.18.1
• debug logs: gitlens.txt
• Video

[axosoft-ramint]

@jkelroy Here's a screenGIF of me attempting the repro steps above (using the repo listed in the steps) and failing to repro (the graph opens). Would you mind confirming if I'm following the steps correctly?

Not sure how to proceed here until I can get a successful repro on my end.

[jkelroy]

@axosoft-ramint one thing I noticed is that you did not close the panel before closing VS Code. If you leave this open, it works as expected.

[eamodio]

Can you please see if this issue is still reproducible in the pre-release edition of GitLens? Thanks!

You can switch to the pre-release edition of GitLens, by clicking on the "Switch to Pre-Release version of this extension" from the Extensions view.