sfdx push failure doesn't return the message

Issue #1321 duplicate
Justin Julicher created an issue

If I have a scratch org that doesn’t have all dependencies installed and I try to deploy I just get:

Pushed 0/1 components to utils in 20 s 17 ms with status 1.

Failures
========
 DeployFailed - Push failed.

but if I do it via sfdx force:source:push I get the full output…

It might be that I’m using the latest version of sfdx?

Comments (4)

  1. Scott Wells repo owner

    Justin, can you run it from the CLI using the --json flag and paste the (likely redacted) output here so I can see if there's something I might be missing. I discussed this with Salesforce at TrailheaDX, but since they don't publish the actual format of the JSON output of these commands, there are sometimes variants that I(/we) don't see/contemplate, in particular with error reporting. Even now I have to handle 3-4 different output formats for errors...sounds like there may be yet another one.

  2. Justin Julicher reporter

    Hi Scott,

    {
        "status": 1,
        "name": "DeployFailed",
        "message": "Push failed.",
        "exitCode": 1,
        "commandName": "SourcePushCommand",
        "stack": "DeployFailed: Push failed.\n    at /home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:63:31\n    at tryCatcher (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/promise.js:510:31)\n    at Promise._settlePromise (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/promise.js:567:18)\n    at Promise._settlePromise0 (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/promise.js:612:10)\n    at Promise._settlePromises (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/promise.js:687:18)\n    at Async._drainQueue (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/async.js:138:16)\n    at Async._drainQueues (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/async.js:148:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/home/jjulicher/.nvm/versions/node/v12.2.0/lib/node_modules/sfdx-cli/node_modules/bluebird/js/release/async.js:17:14)\n    at processImmediate (internal/timers.js:439:21)",
        "warnings": []
    }
    

    looks like an internal SFDX error to me?

    any ideas?

    thanks

  3. Scott Wells repo owner

    Take a look at #1318. It's a regression in the Salesforce CLI when writing output as JSON (which is of course how IC and all other tools integrate with the CLI). I've reported it to Salesforce already so hopefully there will be a quick resolution on their part.

  4. Log in to comment