Invalid checksum in gitIndex

[hmultaniucop]

Getting below error even after updating to latest sf cli

Error (InternalError): An internal error caused this command to fail. isomorphic-git error:
Invalid checksum in GitIndex buffer: expected 44b53f7ed7c05ccc9c922f479d524a607a4d64d9 but saw fb1eab1b06136705b614238e0b303ee46cfff8f3

[github-actions]

Hello @hmultaniucop 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[hmultaniucop]

version 2.94.6-724977b

[iowillhoit]

Hey @hmultaniucop, we have had occasional reports of this over the years. We were able to resolve a related issue in 2023, but haven't seen this much since.

Do you remember which version of the CLI you updated from? Was it a really old version?

Generally, deleting the source tracking files in you projects .sf folder will resolve the issue. Please let me know if you a consistent way to reproduce this error, and we can debug further

[Swizzle4372]

I've been having this issue suddenly too; never had it before. The only fix for me was to delete the ENTIRE .sf/orgs folder, sign out of the orgs and back in again; restarting the IDE between each step. I also updated git for good measure. Tracking was messed up after this so ran sf project tracking reset, now it seems to be functional again

[geoffswift]

In recent times we have been seeing similar issues on an intermittent basis. We have not been able to identify any particular circumstances to reproduce the problem.

[github-actions]

This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.

[Screendead]

I believe I've root-caused this and have a fix ready.

The problem is that isomorphic-git's GitIndexManager uses an in-memory AsyncLock; the actual filesystem lock is commented out. When SF CLI and the VS Code extension both access .sf/orgs/<orgId>/localSourceTracking/index as separate processes, there's nothing coordinating their writes. The isomorphic-git maintainers have said this is the integrator's responsibility (isomorphic-git/isomorphic-git#1828), which means the fix belongs in @salesforce/source-tracking.

I can reproduce this 100% of the time with a standalone script (no org required) - just two Node processes doing concurrent git.add + git.statusMatrix + git.commit against the same isomorphic-git index. Every round corrupts the index badly enough that workers hang trying to parse it. Same root cause as the "Invalid checksum in GitIndex buffer" error, just different corruption patterns depending on exact timing.

isomorphic-git is intentionally a single-process tool, and they insist that it is up to integrators to handle orchestration when using multiple processes - situations like this, where there is a Salesforce VS Code extension working in tandem with an SF CLI tool. Thus, the appropriate place to implement a fix is in @salesforce/source-tracking.

The fix is small: wrap getStatus(), commitChanges(), gitInit(), and delete() in ShadowRepo with a cross-process file lock using lockInit from @salesforce/core (which uses proper-lockfile under the hood, already a transitive dep). No new dependencies.

I intend to open a PR against forcedotcom/source-tracking after getting the appropriate approvals from my company's legal department. Related: #2422, #2483, isomorphic-git/isomorphic-git#1828, isomorphic-git/isomorphic-git#1721.

[mshanemc]

Hey @Screendead that's a great idea.

We've got a very similar bit of code in sfdx-core for trying to protect cross-writes on other files like project/alias/config/etc.

That wrapper around proper-lockfile is exported here

• https://github.com/forcedotcom/sfdx-core/blob/45065f3cbc894e056e1fe7af614817ad0f759f3c/src/index.ts#L105
• https://github.com/forcedotcom/sfdx-core/blob/main/src/util/fileLocking.ts#L31

there's some important "lessons learned" encoded there (esp the bits around browser-based file systems like we're doing with Web Console) that, because it's using source-tracking, should be reused.