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

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: Index file is empty (.git/index) #2476

Closed
Esma-De opened this issue Sep 19, 2023 · 7 comments
Labels
more information required Issue requires more information or a response from the customer stale

Comments

@Esma-De
Copy link

Esma-De commented Sep 19, 2023

Note
Before you submit your issue, make sure that:

  • You're using the latest version of Salesforce CLI. Yes it is 2.8.11
  • You've searched both open and closed issues for related posts.
  • You've used the doctor command to diagnose common issues.
  • You understand that GitHub Issues don't adhere to any agreement or SLA.
    • If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary

When I tried to retrieve or deploy to my sandbox I had this error '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: Index file is empty (.git/index) '

For this org I also had an error "Metadata API request failed: EBUSY: resource busy or locked, open '.sf\org\00D3H0000000PELUA2\localSourceTracking\index'

When I connected my trailhead org and retrieved and deployed there it worked with no error.

Steps To Reproduce

IMPORTANT
Provide a repository that's configured to reproduce the issue. If you are unable to provide a repo, please explain why not. The more info we have from the start, the faster we can resolve your issue.
We may close your issue if you don't include proper instructions.

  • Generate a project with sf project generate or fork dreamhouse-lwc.
  • Provide detailed step-by-step instructions on how to reproduce the issue.

Expected result

Actual result

System Information

PASTE_VERSION_OUTPUT_HERE

Additional information

@Esma-De Esma-De added the investigating We're actively investigating this issue label Sep 19, 2023
@github-actions
Copy link

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.

@github-actions
Copy link

Hello @Esma-De 👋 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 github-actions bot added more information required Issue requires more information or a response from the customer and removed investigating We're actively investigating this issue labels Sep 19, 2023
@mshanemc
Copy link
Contributor

@Esma-De I can't tell from your issue what CLI command you're running.

@bjconover
Copy link

I have ran into this issue before as well. The way that I was able to start pushing/pulling files from Salesforce again was by going to the .sf\orgs(Org ID)\localSourceTracking\index and renaming the index file to a different name. Once I did that I reattempted the send and it created a new index file for me.

@tomansley
Copy link

I have ran into this issue before as well. The way that I was able to start pushing/pulling files from Salesforce again was by going to the .sf\orgs(Org ID)\localSourceTracking\index and renaming the index file to a different name. Once I did that I reattempted the send and it created a new index file for me.

@bjconover how did you know to do that? Your solution worked for me. Nice job!

@github-actions
Copy link

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

@github-actions github-actions bot added the stale label Sep 29, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2023
@Faaiz26
Copy link

Faaiz26 commented Aug 10, 2024

I have ran into this issue before as well. The way that I was able to start pushing/pulling files from Salesforce again was by going to the .sf\orgs(Org ID)\localSourceTracking\index and renaming the index file to a different name. Once I did that I reattempted the send and it created a new index file for me.

your solution works for me , thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more information required Issue requires more information or a response from the customer stale
Projects
None yet
Development

No branches or pull requests

5 participants