File history fails on Git for Windows 2.27 ("There are no editors open that can provide file history information.") #1267
Assignees
Labels
blocked: vscode
Caused by or dependent on a VS Code issue or feature
blocked
Blocked or caused by an upstream issue or feature
bug
Something isn't working
Milestone
Comments
|
Can you try the latest insiders edition to see if this is still reproducible? You can install the insiders edition from here. But be sure to disable/uninstall the stable version of GitLens first. |
eamodio
added
the
needs-more-info
|
2020.12.2104 - sorry, no change. Full output when opening file |
|
YAAAY I think I've figured out how to format collapsible code blocks in github! |
|
@fsackur Hrm, something is definitely going wrong with some path manipulation -- e.g. Could you provide logs for GitLens starting up -- I want to look at the repository discovery code. |
Output - GitLensOutput - GitLens (Git) |
eamodio
removed
inactive
|
Hi - were those logs not what you needed? |
|
@fsackur sorry for the delay. From the logs, it looks like this is an issue with incorrect folder casing -- There is a known issue with VS Code/Git on file systems that aren't case sensitive (Windows, macOS) -- it stems from VS Code not being able to get the correct casing of the folder/file on disk properly, so it basically just uses whatever casing you provide. And Git (unless you set the So to fix this either open the folder/workspace with the exact casing as it exists on disk, or change the Git config to set |
eamodio
added
needs-more-info
|
Bingo! Setting Thanks! I'd be willing to PR a doc update, but I don't see where it would fit (no obvious section in https://gitlens.amod.io/). Shall we just close this issue? It turns up in google searches. |
|
Hrm, unsure why I will add the following notification if GitLens detects this case -- it likely won't be 100% but hopefully it will detect this issue more often than not.
|
eamodio
removed
the
needs-more-info
eamodio
added
blocked
|
After @eamodio added that popup yesterday, some of you will land here because you don't understand why this is suddenly happening. If you're opening the folder from the command line you're probably OK. However, if you're using the Project Manager extension (like many of us multitaskers do), you'll need to "Edit Projects" from that extension. When the JSON file opens, you'll need to verify that the case of the "rootPath" for each project is correct. For the most part, a quick "find and replace" should fix you right up. |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Possibly related to #932
11.0.6git version 2.27.0.windows.11.52.0Win 10Steps to Reproduce:
In the GitLens output, I see, e.g.:
FileHistoryNode(gitlens:repository(c:/githubdata/Build):history:file(file:///c:/githubdata/Build/c:/Githubdata/Build/Public/Add-NestedImportStatement.ps1)).ensureSubscription completed • 10 msThe absolute path is being appended to the repo path, I think. Relevant output:
Full output when opening file
The text was updated successfully, but these errors were encountered: