Long-running sfdx commands #2598
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
|
@Cheffromspace Thanks for posting the logs! I see Do you have anything out of the ordinary in Also, the config code needs to read both So I would try the following:
If either of those help, I'd be great if you could narrow down it down to a specific config var being present or if it's the |
|
Hi @mdonnalley Thank you for your response! The contents of both ~/.sf/config.json and ~/.sfdx/sfdx-config.json are I did rename the .sfdx/sfdx-config.json file. Interestingly my scripted consecutive runs now look like this, times are in seconds: Reproducible: If I wait a minute or two, the first execution takes around 45 seconds while the rest take around 5. Note, I do a lot of work in WSL on the same computer and I'm not seeing any issues there. I use Powershell to run some scripts and was having issues with queries taking a VERY long time to execute. Thus the investigation. I have a function that I manually run from WSL to sync the .sfdx folders so I can use the same auth tokens in either shell that I thought could be contributing but I get the same result even after renaming the entire .sfdx folder in Powershell Log from a long executionLog from short execution |
|
Hi, is there anything else I can do to troubleshoot this? This definitely hasn't gotten any better, on the contrary. How can I find out what's happening during the lull here: 2023-12-07T14:58:51.111Z sf:@salesforce/cli:hooks:prerun start (import) C:\Program Files\sf\client\dist\hooks\prerun.js |
|
@Cheffromspace sorry for the late reply, this is first the prerun hook that gets called: then the telemetry one: and the
So 30s spent in that one, I would start digging into that file first. |
shetzel
added
stale
and removed
investigating
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Running SF commands in powershell occasionally takes a considerable amount of time to run. Even very simple commands like 'sfdx version' which I would expect to run very quickly can take over a minute to run
Steps To Reproduce
Run the command 'sfdx version' (or any sf command)
Expected result
Output the results of the command to stout within a few hundred milliseconds
Actual result
Command will hang for up to 90 seconds. Looking at the logs it appears to hang primarily during the prerun hook of the @salesforce/plugin-telemetry. I have disabled telemetry globally yet the command continues to hang here.
System Information
Powershell 7
{ "architecture": "win32-x64", "cliVersion": "@salesforce/cli/2.20.6", "nodeVersion": "node-v20.9.0", "osVersion": "Windows_NT 10.0.19045", "rootPath": "C:\\Program Files\\sf\\client", "shell": "cmd.exe", "pluginVersions": [ "@oclif/plugin-autocomplete 3.0.2 (core)", "@oclif/plugin-commands 3.0.7 (core)", "@oclif/plugin-help 6.0.7 (core)", "@oclif/plugin-not-found 3.0.4 (core)", "@oclif/plugin-plugins 4.1.8 (core)", "@oclif/plugin-search 1.0.8 (core)", "@oclif/plugin-update 4.1.4 (core)", "@oclif/plugin-version 2.0.8 (core)", "@oclif/plugin-warn-if-update-available 3.0.4 (core)", "@oclif/plugin-which 3.0.11 (core)", "@salesforce/cli 2.20.6 (core)", "apex 3.0.8 (core)", "auth 3.0.8 (core)", "data 3.0.2 (core)", "deploy-retrieve 2.2.0 (core)", "info 3.0.5 (core)", "limits 3.0.4 (core)", "marketplace 1.0.7 (core)", "org 3.0.9 (core)", "packaging 1.27.3 (core)", "schema 3.0.6 (core)", "settings 2.0.9 (core)", "sobject 1.0.2 (core)", "source 3.0.1 (core)", "telemetry 3.1.3 (core)", "templates 56.0.3 (core)", "trust 3.0.6 (core)", "user 3.0.6 (core)" ] }Execution times for 10 runs:
--dev-debug output
Telemetry log
{"eventName":"COMMAND_EXECUTION","platform":"win32","shell":"cmd.exe","arch":"x64","nodeVersion":"v20.9.0","processUptime":43880.4364,"version":"2.20.6","channel":"stable","executable":"sf","origin":"@salesforce/cli/2.20.6 win32-x64 node-v20.9.0","plugin":"@oclif/plugin-version","plugin_version":"2.0.8","command":"version","specifiedFlags":"","specifiedFlagFullNames":"","deprecatedFlagsUsed":"","date":"Thu, 07 Dec 2023 14:26:43 GMT","status":"0","timestamp":"1701959203576","oclif.commandLoadMs":35.57469999790192,"oclif.commandRunMs":30530.87999999523,"oclif.configLoadMs":107.05449998378754,"oclif.corePluginsLoadMs":65.74720001220703,"oclif.initHookMs":1407.21489995718,"oclif.initMs":1408.0674999952316,"oclif.linkedPluginsLoadMs":0,"oclif.postrunHookMs":0.263700008392334,"oclif.prerunHookMs":30487.608500003815,"oclif.runMs":31939.127799987793,"oclif.userPluginsLoadMs":0,"type":"EVENT","cliId":"76ac78e9e51bd25c8863759e348ced93bcba40ed","ci":"bitbucket"}The text was updated successfully, but these errors were encountered: