sfdx force:* hangs when there's an error (no exit code returned)

[bcattaneo]

Summary

When there's an error in any of the force:* commands, process hangs forever without returning an exit code.

Steps To Reproduce:

1. Run any force:* command forcing an error (E.g. sfdx force:org:list wrongparam or sfdx force:org:list --json wrongparam).

Expected result

Process exits returning a (negative) exit code.

Actual result

Process hangs forever, doesn't return an exit code.

Additional information

sfdx force:org:list wrongparam

sfdx force:org:list --json wrongparam

SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.18.0-ee5dc8194c win32-x64 node-v10.15.3

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core):

@oclif/plugin-commands 1.2.2 (core)
@oclif/plugin-help 2.2.0 (core)
@oclif/plugin-not-found 1.2.2 (core)
@oclif/plugin-plugins 1.7.8 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.5 (core)
analytics 1.2.0 (core)
generator 1.1.0 (core)
salesforcedx 46.8.0 (core)
├─ force-language-services 46.12.0 (core)
└─ salesforce-alm 46.11.0 (core)

sfdx-cli 7.18.0 (core)

OS and version: Windows 10

[bcattaneo]

There's a cmdError event which apparently caughts some thrown exceptions on exit (with errors). File is: ...\sfdx\client\7.18.0-ee5dc8194c\node_modules@salesforce\plugin-analytics\lib\hooks\analyticsPrerun.js

After the exception is thrown, it never exits properly. Fixed it on my end adding the following:

// Log command errors to the server.  The ts-ignore is necessary
// because TS is strict about the events that can be handled on process.
// @ts-ignore
process.on('cmdError', async (cmdErr, flags = {}, org) => {
    try {

    }
    catch (err) {

    }
    process.exit(2); // Exit here. Probably needs a proper exit status and not a literal.
});

I hope that helps.

[BobSeu]

Thanks for the temporary solution! I was running into this and it was getting pretty frustrating!

[BobSeu]

Is there any update on when this bug might be fixed?

[clairebianchi]

@BobSeu We are unable to reproduce this issue. Can you please update to the most recent version of the CLI and try again. Also please report issues like these in the Generic CLI repo: https://github.com/forcedotcom/cli/issues

[tnoonan-salesforce]

Also, did you try in a stock windows command.exe instance? Could it be related to Cmder?

[BobSeu]

Sorry for the super delayed response. I think one of the later versions fixed this for me as I'm no longer having the issue. Thanks!

[bcattaneo]

Hello. It did for me as well, thank you.
I'm closing this issue now.