Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dot file cause ininitely hold up for git-lens and git #4116

Open
ICHx opened this issue Feb 27, 2025 · 1 comment
Open

dot file cause ininitely hold up for git-lens and git #4116

ICHx opened this issue Feb 27, 2025 · 1 comment
Labels
needs-more-info Needs further information, steps, details, etc.

Comments

@ICHx
Copy link

ICHx commented Feb 27, 2025

Description

Image

In source control page, clicking any empty dot file like .lock here would cause infinite hold up. Not sure if other observe the same problem

To reproduce

  1. Create an empty dot file in any not-ignored directory inside git repo.
  2. Click the file from git/changes

GitLens Version

16.3.2

VS Code Version

Version: 1.97.2
Commit: e54c774e0add60467559eb0d1e229c6452cf8447
Date: 2025-02-12T23:20:35.343Z
Electron: 32.2.7
ElectronBuildId: 10982180
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

Git Version

No response

Logs, Screenshots, Screen Captures, etc

No response

@ICHx ICHx added the triage Needs to be looked at label Feb 27, 2025
@eamodio eamodio added needs-more-info Needs further information, steps, details, etc. and removed triage Needs to be looked at labels Feb 28, 2025
@eamodio
Copy link
Member

eamodio commented Feb 28, 2025

I can't seem to reproduce this. And if this happens when opening the file from the SCM view there, that is provided by VS Code not GitLens.

If you disable GitLens do you still see the issue?
If so, please report the issue to the VS Code repo.

Otherwise, can 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-more-info Needs further information, steps, details, etc.
Projects
None yet
Development

No branches or pull requests

2 participants