-
-
Notifications
You must be signed in to change notification settings - Fork 384
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
Invalid checksum in GitIndex buffer: expected but saw da39a3ee5e6b4b0d3255bfef95601890afd80709 #1774
Comments
Can you share some details about the error? What software you use, and where this happens? this looks like duplicate of #1733 |
this error stated this week |
You need to contact developers that maintain the software you're using, so they update the library, they break their code and you blame isomorphic git because of the error message. The new error message should say that is wrong with their code. THe problem is that git index is empty which means that the tool you're using deleted the file somehow. |
@jcubic I think the comment in the error message that instructs the user to report the issue to the isomorphic-git project should be removed. I've never found those sorts of suggestions to be productive. |
Agree. The error was supposed to find errors in a library, but this is really annoying because people report here instead of the project they are using. |
I'll try to add a dummy PR with a proper bugfix commit message. |
The issue at foresales: forcedotcom/cli#2194 |
Had the same issue, it was fixed when I deleted the index file after searching for it, the file is mentioned as: .git/index |
Try reporting this to project forcedotcom/cli. I know that the error says to report it here, but the bug is in the Salesforce extension, nothing we can do about the bug in that project. |
An internal error caused this command to fail. Please file a bug report at https://github.com/isomorphic-git/isomorphic-git/issues with this error message: Invalid checksum in GitIndex buffer: expected but saw da39a3ee5e6b4b0d3255bfef95601890afd80709
The text was updated successfully, but these errors were encountered: