History doesn't display for specific project
See original GitHub issueHi! Git History is great, I really appreciate the extension.
I haven’t been able to get it working with my latest project. View History
and View File History
both appear blank:
In the developer console, I get these error messages:
I believe this is related to the first error message E2BIG
, because when testing in another (working) project I still get the other error message t.payload is not iterable
.
This is on a Mac using Git History 0.6.3, VS Code 1.43.2, git 2.23.0. On this project, git log
etc work fine, VS Code’s built-in git utils work fine, and Git Lens works fine.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Can`t see the file history in Gitlens (on a specific project)
My problem is, can`t see the file history or line history in this project. But I can't compare any files with their any...
Read more >View the version history of an item or file in a list or library
Right click on the space between the item or document name and date, and then click Version History from the menu. You might...
Read more >View the activity on your Google Docs, Sheets & Slides
Under "Activity dashboard," turn off Show your view history. If you don't see Activity dashboard or the privacy settings: If the file isn't...
Read more >Local History | IntelliJ IDEA Documentation - JetBrains
Local History helps you constantly track all changes made to a project independently of version control. Unlike version control systems, ...
Read more >Managing project history - SonarQube Documentation
At the project level, from the front page Activity list, choose Show More to see the full activity list. For every snapshot, it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe #541 fixes this as exception is in the same method,
E2BIG
stands for Arg list too long and the solution was to pass arguments in chunks. Windows checks just total length of command so you could get justENAMETOOLONG
, see https://github.com/sanack/node-jq/issues/51#issuecomment-515808932.Yes, it’s working perfectly now (including with default page size of 100)! Thanks @damianfijorek @ole1986, amazing work. So nice to be able to view the history within VS Code.