Issue with project deploy start in CI pipeline #2926
Comments
|
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
bot
added
the
validated
|
I'm facing the same issue locally on my machine. I have had some success with removing both the .sf and .sfdx directories and then setting the default org again. However, this only works for small deployments, setting up a new scratch org with 1k+ components will still run into the same issue again. |
|
I just rebuilt the docker image, but still the same error. We are running "npm install @salesforce/cli --global". |
|
Are you using Linux? |
|
@marcoalmodova No, I'm on MacOS. I also tried going back several sf versions, still the same issue regardless. |
|
@HippieHosenHustler thank for the confirmation, so it's not an OS related problem. But our CI pipeline installs the CLI using npm. |
|
Yes, I had it installed via npm. I tried uninstalling via npm and reinstalling with the installer, but apart from one successful pull of one singular permission set group, it keeps failing with the same error. This is rather frustrating :D |
|
I have no idea why, but it has started to work again. I'm not complaining, but it is weird. Let's see how long it continues to work |
|
@HippieHosenHustler good to hear, but it is still failing here. |
|
There are 2 errors reported. Are both of you seeing both of the errors or just 1? The isomorphic-git error was fixed in that library a while ago so it shouldn't happen. The other error I've never seen before so it would be great to get a stack trace for it. To see debugging output and a stack trace append Does this only happen in your CI environments or do you also see it locally?
Last Friday is when the Summer '24 release started rolling out so it's possibly related to that. CLI releases are on Wednesdays so if it was a regression in the CLI you would have seen it starting Wednesday or Thursday. Also, installing a previous release would fix the issue. |
|
We just started seeing this error |
|
Thanks, Steve. I will try that tomorrow my morning and get back to you here.
…On Mon, 17 Jun 2024, 20:50 Steve Hetzel, ***@***.***> wrote:
We just started seeing this error Metadata API request failed: Cannot
create property 'caller' on string 'incorrect header check' in our tests
on NodeJS version 22.3.0. Looks like this is specific to that version of
NodeJS. Using version 22.2.0 works fine, so I suggest using the LTS NodeJS
version or pinning to 22.2.0.
—
Reply to this email directly, view it on GitHub
<#2926 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJM53X6JP4VAZ7HZI6U5BDZH4VWJAVCNFSM6AAAAABJNNTNWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZUGE4TQNJTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Seeing the same issue @salesforce/cli/2.45.6 win32-x64 node-v22.3.0 Some commands work fine. I can use force:source:deploy as well. |
|
@shetzel node 22.2.0 solved the problem, thanks! Is there a plan to fix the problem with the latest node version? |
|
@marcoalmodova - the bug is not in code that we own. It's in a library called isomorphic-git that most of the plugin-deploy-retrieve commands use. Someone posted an issue for them to fix. It appears they are using a deprecated property on |
|
@shetzel that's what I did. Thanks again! |
|
I'm trying the above suggestions using nvm (including v.22.2.0 and LTS), but not having any luck and am getting the same @salesforce/cli/2.45.6 darwin-arm64 node-v20.4.0 UPDATE: Manually deleting my org's folder from |
|
same issue with the version @salesforce/cli/2.48.0 win32-x64 node-v22.3.0 but if I use the sfdx force:source:deploy |
|
@ALesc21 - please see my post: #2926 (comment) NodeJS recommends using the LTS version for production apps. v22.3.0 is current latest. Switching to the LTS version and using the latest CLI solves the issue. |
|
I had to go back to lts/iron (20) and then I was still having issues with any project that i'd connected while using the node v22, so i recreated my package (in reality, i used time machine to grab my package folder from a week back) and it worked great... there's something that's getting set directly in the project somewhere that remains unresolved once version is downgraded... |
|
I have also gone back to node 15. See attached trace files. [17:10:02.089] DEBUG (sf:oclif:find-root:root-plugin): Finding root plugin using /opt/homebrew/lib/node_modules/@salesforce/cli/dist 2024-06-27T07:10:02.656Z sf:telemetry Usage acknowledgement file already exists *** Internal Diagnostic *** TypeError: Cannot create property 'caller' on string 'incorrect header check' 2024-06-27T07:10:05.864Z sf:telemetry Spawning "/opt/homebrew/Cellar/node@20/20.15.0/bin/node /opt/homebrew/lib/node_modules/@salesforce/cli/node_modules/@salesforce/plugin-telemetry/processes/upload.js /Users/pbw/Library/Caches/sf /var/folders/jf/mkyz74311796dl4mxx_7tcx80000gn/T/sf-telemetry/telemetry-915aa158ab76a33aa361203371786d946e21f1ba.log" |
|
Hey 👋, Hope it helps! :) |
|
Also on MacOS. My problem has been (temporarily?) solved by uninstalling @salesforce/* packages, previously installed using my homebrew instance of node 20.15.0 (installed as node@200), and then installing using the salesforce-cli package for Apple silicon from https://developer.salesforce.com/tools/salesforcecli. I also restarted VS Code to pick up pending updates. |
|
today's node ( If you're still able to reproduce this with a current CLI and current nodejs version, please open a new issue with the details! |
Summary
When running project deploy start through CI, one of the following error happens:
SHA check failed! Expected 6a8101cdb9fb777eca3646dc9ac5b27180551286, computed e50f26defea06e7dc1ce70441600fcc6fb1ac392
It happened with the current cli version and I even tried to update to the rc version, but no success.
Steps To Reproduce
Run a basic CI pipeline and try to deploy start with the existing metadata. I also tried with a pretty empty project (two classes only).
Expected result
The deployment happening successfully.
Actual result
The errors described in the summary section happen.
System Information
{ "architecture": "linux-x64", "cliVersion": "@salesforce/cli/2.45.6", "nodeVersion": "node-v22.3.0", "osVersion": "Linux 5.15.0-1057-aws", "rootPath": "/usr/local/lib/node_modules/@salesforce/cli", "shell": "bash", "pluginVersions": [ "@oclif/plugin-autocomplete 3.1.2 (core)", "@oclif/plugin-commands 4.0.2 (core)", "@oclif/plugin-help 6.1.0 (core)", "@oclif/plugin-not-found 3.2.2 (core)", "@oclif/plugin-plugins 5.2.2 (core)", "@oclif/plugin-search 1.1.1 (core)", "@oclif/plugin-update 4.3.3 (core)", "@oclif/plugin-version 2.2.2 (core)", "@oclif/plugin-warn-if-update-available 3.1.4 (core)", "@oclif/plugin-which 3.2.1 (core)", "@salesforce/cli 2.45.6 (core)", "apex 3.1.14 (core)", "auth 3.6.17 (core)", "community 3.2.18 (user) published 4 days ago (Thu Jun 13 2024) (latest is 3.2.19)", "data 3.4.3 (core)", "deploy-retrieve 3.8.4 (core)", "info 3.3.4 (core)", "limits 3.3.10 (core)", "marketplace 1.2.10 (core)", "org 4.1.19 (core)", "packaging 2.4.6 (user) published 10 days ago (Thu Jun 06 2024)", "schema 3.3.10 (core)", "settings 2.3.0 (core)", "sobject 1.4.8 (core)", "source 3.3.21 (core)", "telemetry 3.3.12 (core)", "templates 56.2.9 (core)", "trust 3.7.4 (core)", "user 3.5.11 (core)", "sfdx-git-delta 5.40.2 (user) published 3 days ago (Thu Jun 13 2024)" ] }Additional information
The text was updated successfully, but these errors were encountered: