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

Salseforce CLI does not release the running process when finished executing #2450

Closed
justin-lyon opened this issue Sep 6, 2023 · 4 comments
Labels
more information required Issue requires more information or a response from the customer validated Version information for this issue has been validated

Comments

@justin-lyon
Copy link

Summary

For all sf and sfdx commands, the running process is not released immediately after completing execution. Instead sf keeps the process open for a few seconds delay after the output has already been reported to standard out.

Steps To Reproduce

  1. Execute sf version or sfdx version in your terminal.
  2. Notice the version is instantly printed to standard out
  3. Notice it takes ~10 seconds to release the process back to the terminal
Screen.Recording.2023-09-06.at.10.11.57.AM.mov

Expected result

After the command reports to standard out, it should release the process back to the user.

Actual result

After the command reports to standard out, it hangs for ~10 seconds before releasing back to the user.

System Information

zsh

{
  "cliVersion": "@salesforce/cli/2.6.9",
  "architecture": "darwin-arm64",
  "nodeVersion": "node-v18.1.0",
  "osVersion": "Darwin 22.4.0",
  "shell": "zsh",
  "rootPath": "/Users/justin/.nvm/versions/node/v18.1.0/lib/node_modules/@salesforce/cli",
  "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.9 (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)",
    "packaging 1.16.5 (user)",
    "schema 2.3.23 (core)",
    "settings 1.4.26 (core)",
    "signups 1.4.33 (user)",
    "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

@justin-lyon justin-lyon added the investigating We're actively investigating this issue label Sep 6, 2023
@github-actions github-actions bot added the validated Version information for this issue has been validated label Sep 6, 2023
@github-actions
Copy link

github-actions bot commented Sep 6, 2023

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.

@mshanemc
Copy link
Contributor

mshanemc commented Sep 6, 2023

hey @justin-lyon someone from our team did see this--it was fixed by updating the node version (18.17.1 is current, I think that very early 18.1.0 is the problem).

Can you try and let us know?

@mshanemc mshanemc 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 6, 2023
@AllanOricil
Copy link

It would be good if ocliff could verify the supported node version before running any command. Useful for people, like me, who have multiple node version in their machines.

@justin-lyon
Copy link
Author

Thanks @mshanemc. That seems to be it. After updating my node version, I don't experience these delays any longer.

@mshanemc mshanemc closed this as completed Sep 7, 2023
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 validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

3 participants