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

Cannot deploy with VsCode : sf (V2) #2441

Closed
ktainter opened this issue Aug 31, 2023 · 12 comments
Closed

Cannot deploy with VsCode : sf (V2) #2441

ktainter opened this issue Aug 31, 2023 · 12 comments
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue validated Version information for this issue has been validated

Comments

@ktainter
Copy link

Summary

Invalid checksum in GitIndex buffer: expected 7da376a907329963834340460055666f7263652d but saw 7200008d8f63bef57035e92afd3ef9b6b30a2db2

I receive the above message when trying to use the vsCode option command to deploy to an org.

Steps To Reproduce

I cannot provide a repo, the work is proprietary. However, I can confirm that the same behavior exists in a Salesforce Playground connected to VsCode in a different project

PS C:\Users\kerrie.tainter\Desktop<project directory> sf project start deploy -x manifest\OGP-xxxx.xml
Error (1): An internal error caused this command to fail. Please file a bug report at https://itIndex buffer: expected 7da376a907329963834340460055666f7263652d but saw 7200008d8f63bef57035e92afd3ef9b6b30a2db2

Expected result

C:\Users\kerrie.tainter\Desktop<project directory> sf force:source:deploy -x manifest\OGP-xxxx.xml
Warning: We plan to deprecate this command in the future. Try using the "project deploy start" command instead.
Deploying v59.0 metadata to using the v59.0 SOAP API.
Deploy ID: xxxxQSA3
DEPLOY PROGRESS | ████████████████████████████████████████ | 1/1 Components

=== Deployed Source
...

Actual result

System Information

VsCode Powershell

{
  "cliVersion": "@salesforce/cli/2.6.7",
  "architecture": "win32-x64",
  "nodeVersion": "node-v18.15.0",
  "osVersion": "Windows_NT 10.0.19045",
  "shell": "cmd.exe",
  "rootPath": "C:\\Program Files\\sf\\client",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.6 (core)",
    "@oclif/plugin-commands 2.2.23 (core)",
    "@oclif/plugin-help 5.2.17 (core)",
    "@oclif/plugin-not-found 2.3.37 (core)",
    "@oclif/plugin-plugins 3.2.7 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.1.32 (core)",
    "@oclif/plugin-version 1.3.8 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.48 (core)",
    "@oclif/plugin-which 2.2.31 (core)",
    "@salesforce/cli 2.6.7 (core)",
    "apex 2.3.11 (core)",
    "auth 2.8.13 (core)",
    "data 2.5.7 (core)",
    "deploy-retrieve 1.17.5 (core)",
    "info 2.6.39 (core)",
    "limits 2.3.31 (core)",
    "login 1.2.28 (core)",
    "org 2.10.3 (core)",
    "schema 2.3.23 (core)",
    "settings 1.4.26 (core)",
    "sobject 0.2.6 (core)",
    "source 2.10.32 (core)",
    "telemetry 2.3.1 (core)",
    "templates 55.5.10 (core)",
    "trust 2.6.3 (core)",
    "user 2.3.29 (core)"
  ]
}```
### Additional information
@ktainter ktainter added the investigating We're actively investigating this issue label Aug 31, 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 github-actions bot added the validated Version information for this issue has been validated label Aug 31, 2023
@Schuchie
Copy link

Schuchie commented Sep 4, 2023

I am also affected by this

@daniil-rozin-itechart
Copy link

I have the same issue (@salesforce/cli/2.6.7 win32-x64 node-v18.15.0)

@olektymchenko
Copy link

I had the same error when created a new project
Connection version was 58.0 but created sfdx-project was 59.0, chaning sfdx-project to 58.0 helps

@Schuchie
Copy link

Schuchie commented Sep 4, 2023

We are on all projects on API 58 and still the problem occurs
@salesforce/cli/2.6.7 darwin-arm64 node-v18.11.0

@alighieth09
Copy link

I am using API 58, and still facing the same issue, @salesforce/cli/2.6.7 darwin-x64 node-v18.15.0

@KeypeG
Copy link

KeypeG commented Sep 7, 2023

Facing the exact same issue since a few days, updating sf didn't make any difference, uninstalling / reinstalling cleared the issue, it reappeared today.
Updated sf again, didn't make any difference.
@salesforce/cli/2.7.11 win32-x64 node-v18.15.0

@djtoohey
Copy link

djtoohey commented Sep 7, 2023

I'll just add what worked for me for anyone else who comes across this issue,
I deleted the local copy of the repo I was pushing from, re cloned it, pushed with no issues.
In hindsight git gc could have probably been all that was needed.
Hope this helps

FYI: @KeypeG @alighieth09 @Schuchie @olektymchenko @daniil-rozin-itechart

@daniil-rozin-itechart
Copy link

@djtoohey It helped me, thanks a lot !

@alighieth09
Copy link

@djtoohey this solved the issue thanks alot!

@mshanemc mshanemc added the bug Issue or pull request that identifies or fixes a bug label Sep 20, 2023
@git2gus
Copy link

git2gus bot commented Sep 20, 2023

This issue has been linked to a new work item: W-14155089

@iowillhoit
Copy link
Contributor

We believe that this issue has been resolved. Please make sure you are using the latest version of sf (currently 2.12.9) and the latest version of the Salesforce VSCode extension. If you are still having issues, please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

9 participants