Trying to retrieve a single file via VSCode with Salesforce Extensions is taking an excessive amount of time. This behaviour has been seen on two different machines (Windows & Mac) over several days so think we can rule out network glitch.

SFDX CLI version - sfdx-cli/6.44.0-dead729fb5 (darwin-x64) node-v8.9.4
VSCode Version - Version 1.30.2 (1.30.2)

Instead of printing the exit code for CLI command executions we should display more meaningful messages.

... ended with exit code 0 should instead be ... succeded (exit code 0).

... ended with exit code 1 should instead be ... failed (exit code 1).

Ideally, there would also be a short line of what the failure type was:

... ended with exit code 1 should instead be ... failed because of XYZ (exit code 1).

Summary

After custom object deletions in a scratch org, files related to profile are not updated by sfdx force:source:pull command.

Steps To Reproduce:

1. Create a new scratch org.
2. Open the new scratch org.
3. Create a new Custom Object.
4. Retrieve modified metadata with sfdx force:source:pull
5. Verify the profile files are referencing, for instance, the new custom object layouts.
6. In the scratch org, delete the created Custom Object
7. Retrieve the metadata using sfdx force:source:pull again

Expected result

The *.profile-meta.xml files doesn't contain any reference to deleted custom object assets.

Actual result

The *.profile-meta.xml files keeps references to deleted custom object assets. This will cause failure to any upcoming sfdx force:source:push execution.

Additional information

Created Object:

Retrieved metadata using sfdx force:source:pull

Retrieved metadata after custom object deletion.

Content of profile-meta.xml files after custom object deletion and pulling of scratch org source code.

ERROR: result of sfdx force:source:push -f into a new scratch org with the last pulled source code version:

SFDX CLI Version: sfdx-cli/6.50.0-9817aece8a (darwin-x64) node-v8.9.4

OS and version: darwin18 (MacOS Mojave)

Summary

Attempting to deploy a new Contact sharing rule using force:source:deploy -x package.xml

Steps To Reproduce:

1. Create an owner sharing rule for the Contact object named MyOwnerSharingRule and retrieve metadata
2. Create a package.xml file that includes the following content:

<types>
    <members>Contact.MyOwnerSharingRule</members>
    <name>SharingOwnerRule</name>
</types>

3. Run sfdx command:

sfdx force:source:deploy -x package.xml

4. The following error message is returned:

The SharingOwnerRule named Contact.MyOwnerSharingRule was not found in the workspace.

5. Update the package.xml file as follows:

<types>
    <members>Contact.*</members>
    <name>SharingOwnerRule</name>
</types>

6. Run sfdx command:

sfdx force:source:deploy -x package.xml

7. No error is returned but sharing rule is not deployed

Expected result

Sharing rule should appear under Contact Sharing Rules

Actual result

Either an error is returned or metadata is ignored. See Steps To Reproduce for details.

SFDX CLI Version:
(sfdx --version) sfdx-cli/6.48.0-bfccc40118 (windows-x64) node-v8.9.4
(sfdx force --version) v44.0

OS and version:
Windows 7 64-bit

Deploy using Circle ci and getting an error with WInter 19 orgs.

sfdx force:config:set apiVersion=44.0 --global
sfdx force:source:convert -d deploy_prod -r force-app
sfdx force:mdapi:deploy -u deployTarget -d deploy_prod/ -w -1 -l

OS and version:

Is your feature request related to a problem? Please describe.
Today there is no simple way to retrieve package information through Salesforce CLI. There is a need to parse sfdx-project.json and then use two Tooling API calls to retrieve package and package version information for a given alias.

What are you trying to do
A description of the outcome you are hoping to achieve
Retrieve package information to display in build log and to retrieve the installation key from a secret text in Jenkins. This is also useful for local development.

Describe the solution you'd like
Would like to have another command in force:package that could retrieve package information. Could be something lke force:package:version:info.

Describe alternatives you've considered
Currently, I have implemented this as a Groovy script for Jenkins but I'm also considering writing a plugin.

What are you trying to do
I would like to be able to specify a -x, --sandbox flag instead having to type out https://test.salesforce.com for the -r, --instanceurl flag, each time I want to authenticate with a sandbox org.

Examples:

$ sfdx force:auth:web:login --sandbox --setalias sandbox1
$ sfdx force:auth:web:login -x -a sandbox2

Summary

It seems like if your pacakge.xml has any metadata components listed that do not exist in your force-app, that it fails.

Steps To Reproduce:

1. sfdx force:source:retrieve -- manifest in VS Code pull source from Org with a Package.xml file
2. change orgs in VS Code to a new sandbox
3. sfdx force:source:deploy --manifest /manifest/package.xml with the VS code right click

get the error ERROR: Cannot read property 'getMetadataName' of undefined.

Expected result

unless you have undeployable metadata components in your package.xml, you should be able to use the same package.xml to both source:retrieve and source:deploy

Actual result

If mtetadata defined in your package.xml returns no files, then that folder is not created in force-app. then when you try to deploy you get ERROR: Cannot read property 'getMetadataName' of undefined.

Additional information

VSCode output window:

Starting SFDX: Deploy Source to Org

sfdx force:source:deploy --manifest /project/manifest/package.xml
WARNING: apiVersion configuration overridden at 43.0
ERROR:  Cannot read property 'getMetadataName' of undefined.
sfdx force:source:deploy --manifest /project/manifest/package.xml ended with exit code 1

VS Code Version:
OSX Version 1.26.1 (1.26.1)

SFDX CLI Version:
sfdx-cli/6.29.0 (darwin-x64) node-v8.11.2

OS and version:
OSX 10.12.6

Summary

We have experienced serious adoption issues from developers of CLI and DX due to the performance on our Windows PCs. Would love to partner with you to get more data if it means improving the experience.

Running all commands via Git Bash (or Bash terminal within Code). We seem to have performance issues whether we are on corporate network (on-prem or VPN) or working disconnected.

Landed here based on tweet from @ntotten:

I created a wiki with instructions on how to gather the logs and info we need: https://t.co/5VM8YG4qZa

— Nathan Totten (@ntotten) January 31, 2019

SFDX CLI Version:

~ $ sfdx -v
sfdx-cli/6.52.2-c6cdc99881 (windows-x64) node-v8.9.4

SFDX plugin Version:

~/Projects/salesforce/puppeteer (master) $ sfdx plugins --core
@salesforce/plugin-generator 1.0.1 (core)
@salesforce/sfdx-trust 2.0.1 (core)
builtins 1.0.0 (core)
salesforcedx 44.5.0

Open Org:

~/Projects/salesforce/puppeteer (master) $ DEBUG=* sfdx force:org:open
2019-02-15T15:53:20.971Z cli starting run
2019-02-15T15:53:21.664Z cli checking autoupdater
2019-02-15T15:53:21.673Z rwlockfile read C:\Users\{user}\AppData\Local\sfdx\update.lock
2019-02-15T15:53:21.748Z cli-engine:hooks init C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\plugins\migrate.js
2019-02-15T15:53:23.149Z sfdx:hook:init:plugins:migrate enter
2019-02-15T15:53:23.165Z sfdx:plugins:migrate no v5 plugins need migration
2019-02-15T15:53:23.165Z sfdx:hook:init:plugins:migrate exit
2019-02-15T15:53:23.166Z cli dispatcher
2019-02-15T15:53:47.931Z cli-engine:hooks plugins:parse C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\plugins\convertFromV5.js
2019-02-15T15:53:47.970Z sfdx:hook:plugins:parse:legacy enter
2019-02-15T15:53:47.971Z sfdx:hook:plugins:parse:legacy exit
2019-02-15T15:53:48.046Z cli-engine:hooks plugins:parse C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\plugins\convertFromV5.js
2019-02-15T15:53:48.046Z sfdx:hook:plugins:parse:legacy enter
2019-02-15T15:53:48.046Z sfdx:hook:plugins:parse:legacy exit
2019-02-15T15:53:48.100Z cli-engine:hooks prerun C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\logAnalytics.js
2019-02-15T15:53:48.105Z sfdx:hook:analytics enter
2019-02-15T15:53:48.106Z sfdx:analytics setting up exit handler
2019-02-15T15:53:48.106Z sfdx:hook:analytics exit
2019-02-15T15:53:48.113Z cli running flow command { _version: '9.0.7' }
(node:21476) DeprecationWarning: this.out and this.cli is deprecated. Please import the "cli-ux" module directly instead.
(node:21476) DeprecationWarning: cli.color is deprecated. Please use `import color from '@heroku-cli/color'` instead.
Access org 00D1100000BvrpPEAR as user [email protected] with the following URL: https://platform-saas-4489-dev-ed.cs18.my.salesforce.com//secur/frontdoor.jsp?sid=00D1100000BvrpP!AREAQAPOO.aqWmpdqZWwsAYCqJtDvCmQGytnfhPfZmxhZV3TroYK4GtF4cFAGbxTdgyFyBlEO2pD4I5RhqX.A3urSiGzLYf.
2019-02-15T15:54:10.932Z cli flushing stdout
2019-02-15T15:54:10.936Z sfdx:analytics using C:\Users\{user}\AppData\Local\sfdx\analytics.log for usage error logging
2019-02-15T15:54:11.184Z sfdx:analytics spawned usage "C:\Users\{user}\AppData\Local\sfdx\client\bin\node.exe C:\Users\{user}\AppData\Local\sfdx\client\dist\processes\logUsage"

Source push

~/Projects/salesforce/puppeteer (master) $ DEBUG=* sfdx force:source:push
2019-02-15T16:05:24.465Z cli starting run
2019-02-15T16:05:25.658Z cli checking autoupdater
2019-02-15T16:05:25.730Z rwlockfile read C:\Users\{user}\AppData\Local\sfdx\update.lock
2019-02-15T16:05:26.160Z cli-engine:hooks init C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\plugins\migrate.js
2019-02-15T16:05:28.002Z sfdx:hook:init:plugins:migrate enter
2019-02-15T16:05:28.012Z sfdx:plugins:migrate no v5 plugins need migration
2019-02-15T16:05:28.012Z sfdx:hook:init:plugins:migrate exit
2019-02-15T16:05:28.013Z cli dispatcher
2019-02-15T16:05:57.543Z cli-engine:hooks plugins:parse C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\plugins\convertFromV5.js
2019-02-15T16:05:57.585Z sfdx:hook:plugins:parse:legacy enter
2019-02-15T16:05:57.587Z sfdx:hook:plugins:parse:legacy exit
2019-02-15T16:05:57.684Z cli-engine:hooks plugins:parse C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\plugins\convertFromV5.js
2019-02-15T16:05:57.684Z sfdx:hook:plugins:parse:legacy enter
2019-02-15T16:05:57.684Z sfdx:hook:plugins:parse:legacy exit
2019-02-15T16:05:57.715Z cli-engine:hooks prerun C:\Users\{user}\AppData\Local\sfdx\client\dist\hooks\logAnalytics.js
2019-02-15T16:05:57.719Z sfdx:hook:analytics enter
2019-02-15T16:05:57.719Z sfdx:analytics setting up exit handler
2019-02-15T16:05:57.719Z sfdx:hook:analytics exit
2019-02-15T16:05:57.725Z cli running flow command { _version: '9.0.7' }
(node:24512) DeprecationWarning: this.out and this.cli is deprecated. Please import the "cli-ux" module directly instead.
(node:24512) DeprecationWarning: cli.color is deprecated. Please use `import color from '@heroku-cli/color'` instead.
2019-02-15T16:06:02.240Z sfdx:core TRACE Setup child 'SourceUtil' logger instance
2019-02-15T16:06:02.248Z sfdx:SourceUtil INFO Created output directory 'C:\Users\{user}\AppData\Local\Temp\sdx_mdpkg_1550246762240'
2019-02-15T16:06:02.256Z sfdx:core TRACE Setup child 'SourceUtil' logger instance
2019-02-15T16:06:02.258Z sfdx:SourceUtil INFO Created output directory 'C:\Users\{user}\AppData\Local\Temp\sdx_decomposition_1550246762256'
2019-02-15T16:06:03.376Z sfdx:core TRACE Setup child 'SourceUtil' logger instance
2019-02-15T16:06:03.421Z sfdx:SourceUtil WARN Could not delete the outputDir 'C:\Users\{user}\AppData\Local\Temp\sdx_decomposition_1550246762256' due to: ENOENT: no such file or directory, stat 'C:\Users\{user}\AppData\Local\Temp\sdx_decomposition_1550246762256.zip'
2019-02-15T16:06:22.474Z sfdx:core TRACE Setup child 'SourceUtil' logger instance
2019-02-15T16:06:22.580Z sfdx:SourceUtil WARN Could not delete the outputDir 'C:\Users\{user}\AppData\Local\Temp\sdx_mdpkg_1550246762240' due to: ENOTDIR: not a directory, scandir 'C:\Users\{user}\AppData\Local\Temp\sdx_mdpkg_1550246762240.zip'
=== Pushed Source
STATE  FULL NAME                                                           TYPE                  PROJECT PATH
─────  ──────────────────────────────────────────────────────────────────  ────────────────────  ──────────────────────────────────────────────────────────────────────────────────────────────────────────────
Add    egApplicationEvent\egApplicationEvent.auradoc                       AuraDefinitionBundle  lightning-component-tests\main\default\aura\egApplicationEvent\egApplicationEvent.auradoc
Add    egApplicationEvent\egApplicationEvent.evt                           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egApplicationEvent\egApplicationEvent.evt
Add    egApplicationEvent\egApplicationEvent.evt                           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egApplicationEvent\egApplicationEvent.evt-meta.xml
Add    egAttributeTypes\egAttributeTypes.auradoc                           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egAttributeTypes\egAttributeTypes.auradoc
Add    egAttributeTypes\egAttributeTypes.cmp                               AuraDefinitionBundle  lightning-component-tests\main\default\aura\egAttributeTypes\egAttributeTypes.cmp
Add    egAttributeTypes\egAttributeTypes.cmp                               AuraDefinitionBundle  lightning-component-tests\main\default\aura\egAttributeTypes\egAttributeTypes.cmp-meta.xml
Add    egAttributeTypes\egAttributeTypesController.js                      AuraDefinitionBundle  lightning-component-tests\main\default\aura\egAttributeTypes\egAttributeTypesController.js
Add    egClientSideAction\egClientSideAction.auradoc                       AuraDefinitionBundle  lightning-component-tests\main\default\aura\egClientSideAction\egClientSideAction.auradoc
Add    egClientSideAction\egClientSideAction.cmp                           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egClientSideAction\egClientSideAction.cmp
Add    egClientSideAction\egClientSideAction.cmp                           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egClientSideAction\egClientSideAction.cmp-meta.xml
Add    egClientSideAction\egClientSideActionController.js                  AuraDefinitionBundle  lightning-component-tests\main\default\aura\egClientSideAction\egClientSideActionController.js
Add    egClientSideAction\egClientSideActionHelper.js                      AuraDefinitionBundle  lightning-component-tests\main\default\aura\egClientSideAction\egClientSideActionHelper.js
Add    egComponentEvent\egComponentEvent.auradoc                           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentEvent\egComponentEvent.auradoc
Add    egComponentEvent\egComponentEvent.evt                               AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentEvent\egComponentEvent.evt
Add    egComponentEvent\egComponentEvent.evt                               AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentEvent\egComponentEvent.evt-meta.xml
Add    egComponentMethod\egComponentMethod.auradoc                         AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentMethod\egComponentMethod.auradoc
Add    egComponentMethod\egComponentMethod.cmp                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentMethod\egComponentMethod.cmp
Add    egComponentMethod\egComponentMethod.cmp                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentMethod\egComponentMethod.cmp-meta.xml
Add    egComponentMethod\egComponentMethodController.js                    AuraDefinitionBundle  lightning-component-tests\main\default\aura\egComponentMethod\egComponentMethodController.js
Add    egConditionalUI\egConditionalUI.auradoc                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egConditionalUI\egConditionalUI.auradoc
Add    egConditionalUI\egConditionalUI.cmp                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egConditionalUI\egConditionalUI.cmp
Add    egConditionalUI\egConditionalUI.cmp                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egConditionalUI\egConditionalUI.cmp-meta.xml
Add    egConditionalUI\egConditionalUIController.js                        AuraDefinitionBundle  lightning-component-tests\main\default\aura\egConditionalUI\egConditionalUIController.js
Add    egEventHandling\egEventHandling.auradoc                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egEventHandling\egEventHandling.auradoc
Add    egEventHandling\egEventHandling.cmp                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egEventHandling\egEventHandling.cmp
Add    egEventHandling\egEventHandling.cmp                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egEventHandling\egEventHandling.cmp-meta.xml
Add    egEventHandling\egEventHandlingController.js                        AuraDefinitionBundle  lightning-component-tests\main\default\aura\egEventHandling\egEventHandlingController.js
Add    egFacet\egFacet.auradoc                                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egFacet\egFacet.auradoc
Add    egFacet\egFacet.cmp                                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egFacet\egFacet.cmp
Add    egFacet\egFacet.cmp                                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egFacet\egFacet.cmp-meta.xml
Add    egGlobalValueProvider\egGlobalValueProvider.auradoc                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egGlobalValueProvider\egGlobalValueProvider.auradoc
Add    egGlobalValueProvider\egGlobalValueProvider.cmp                     AuraDefinitionBundle  lightning-component-tests\main\default\aura\egGlobalValueProvider\egGlobalValueProvider.cmp
Add    egGlobalValueProvider\egGlobalValueProvider.cmp                     AuraDefinitionBundle  lightning-component-tests\main\default\aura\egGlobalValueProvider\egGlobalValueProvider.cmp-meta.xml
Add    egLdsView\egLdsView.auradoc                                         AuraDefinitionBundle  lightning-component-tests\main\default\aura\egLdsView\egLdsView.auradoc
Add    egLdsView\egLdsView.cmp                                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egLdsView\egLdsView.cmp
Add    egLdsView\egLdsView.cmp                                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egLdsView\egLdsView.cmp-meta.xml
Add    egLdsView\egLdsViewController.js                                    AuraDefinitionBundle  lightning-component-tests\main\default\aura\egLdsView\egLdsViewController.js
Add    egLdsView\egLdsViewHelper.js                                        AuraDefinitionBundle  lightning-component-tests\main\default\aura\egLdsView\egLdsViewHelper.js
Add    egRenderElement\egRenderElement.auradoc                             AuraDefinitionBundle  lightning-component-tests\main\default\aura\egRenderElement\egRenderElement.auradoc
Add    egRenderElement\egRenderElement.cmp                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egRenderElement\egRenderElement.cmp
Add    egRenderElement\egRenderElement.cmp                                 AuraDefinitionBundle  lightning-component-tests\main\default\aura\egRenderElement\egRenderElement.cmp-meta.xml
Add    egServerSideActionCallback\egServerSideActionCallback.auradoc       AuraDefinitionBundle  lightning-component-tests\main\default\aura\egServerSideActionCallback\egServerSideActionCallback.auradoc
Add    egServerSideActionCallback\egServerSideActionCallback.cmp           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egServerSideActionCallback\egServerSideActionCallback.cmp
Add    egServerSideActionCallback\egServerSideActionCallback.cmp           AuraDefinitionBundle  lightning-component-tests\main\default\aura\egServerSideActionCallback\egServerSideActionCallback.cmp-meta.xml
Add    egServerSideActionCallback\egServerSideActionCallbackController.js  AuraDefinitionBundle  lightning-component-tests\main\default\aura\egServerSideActionCallback\egServerSideActionCallbackController.js
Add    egServerSideActionCallback\egServerSideActionCallbackHelper.js      AuraDefinitionBundle  lightning-component-tests\main\default\aura\egServerSideActionCallback\egServerSideActionCallbackHelper.js
Add    egServerSideActionController                                        ApexClass             lightning-component-tests\main\default\classes\egServerSideActionController.cls
Add    egServerSideActionController                                        ApexClass             lightning-component-tests\main\default\classes\egServerSideActionController.cls-meta.xml
Add    CustomLabels                                                        CustomLabels          lightning-component-tests\main\default\labels\CustomLabels.labels-meta.xml
Add    jasmineTests\jasmineTests.app                                       AuraDefinitionBundle  lightning-component-tests\test\default\aura\jasmineTests\jasmineTests.app
Add    jasmineTests\jasmineTests.app                                       AuraDefinitionBundle  lightning-component-tests\test\default\aura\jasmineTests\jasmineTests.app-meta.xml
Add    jasmineTests\jasmineTests.auradoc                                   AuraDefinitionBundle  lightning-component-tests\test\default\aura\jasmineTests\jasmineTests.auradoc
Add    lts_jasmineRunner\lts_jasmineRunner.auradoc                         AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_jasmineRunner\lts_jasmineRunner.auradoc
Add    lts_jasmineRunner\lts_jasmineRunner.cmp                             AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_jasmineRunner\lts_jasmineRunner.cmp
Add    lts_jasmineRunner\lts_jasmineRunner.cmp                             AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_jasmineRunner\lts_jasmineRunner.cmp-meta.xml
Add    lts_jasmineRunner\lts_jasmineRunnerController.js                    AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_jasmineRunner\lts_jasmineRunnerController.js
Add    lts_mochaRunner\lts_mochaRunner.auradoc                             AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_mochaRunner\lts_mochaRunner.auradoc
Add    lts_mochaRunner\lts_mochaRunner.cmp                                 AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_mochaRunner\lts_mochaRunner.cmp
Add    lts_mochaRunner\lts_mochaRunner.cmp                                 AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_mochaRunner\lts_mochaRunner.cmp-meta.xml
Add    lts_mochaRunner\lts_mochaRunnerController.js                        AuraDefinitionBundle  lightning-component-tests\test\default\aura\lts_mochaRunner\lts_mochaRunnerController.js
Add    mochaTests\mochaTests.app                                           AuraDefinitionBundle  lightning-component-tests\test\default\aura\mochaTests\mochaTests.app
Add    mochaTests\mochaTests.app                                           AuraDefinitionBundle  lightning-component-tests\test\default\aura\mochaTests\mochaTests.app-meta.xml
Add    mochaTests\mochaTests.auradoc                                       AuraDefinitionBundle  lightning-component-tests\test\default\aura\mochaTests\mochaTests.auradoc
Add    jasmineExampleTests                                                 StaticResource        lightning-component-tests\test\default\staticresources\jasmineExampleTests.resource
Add    jasmineExampleTests                                                 StaticResource        lightning-component-tests\test\default\staticresources\jasmineExampleTests.resource-meta.xml
Add    jasmineHelloWorldTests                                              StaticResource        lightning-component-tests\test\default\staticresources\jasmineHelloWorldTests.resource
Add    jasmineHelloWorldTests                                              StaticResource        lightning-component-tests\test\default\staticresources\jasmineHelloWorldTests.resource-meta.xml
Add    jasmineLightningDataServiceTests                                    StaticResource        lightning-component-tests\test\default\staticresources\jasmineLightningDataServiceTests.resource
Add    jasmineLightningDataServiceTests                                    StaticResource        lightning-component-tests\test\default\staticresources\jasmineLightningDataServiceTests.resource-meta.xml
Add    lts_chai                                                            StaticResource        lightning-component-tests\test\default\staticresources\lts_chai.resource
Add    lts_chai                                                            StaticResource        lightning-component-tests\test\default\staticresources\lts_chai.resource-meta.xml
Add    lts_jasmine                                                         StaticResource        lightning-component-tests\test\default\staticresources\lts_jasmine.resource
Add    lts_jasmine                                                         StaticResource        lightning-component-tests\test\default\staticresources\lts_jasmine.resource-meta.xml
Add    lts_jasmineboot                                                     StaticResource        lightning-component-tests\test\default\staticresources\lts_jasmineboot.resource
Add    lts_jasmineboot                                                     StaticResource        lightning-component-tests\test\default\staticresources\lts_jasmineboot.resource-meta.xml
Add    lts_mochaBootJs                                                     StaticResource        lightning-component-tests\test\default\staticresources\lts_mochaBootJs.resource
Add    lts_mochaBootJs                                                     StaticResource        lightning-component-tests\test\default\staticresources\lts_mochaBootJs.resource-meta.xml
Add    lts_mochaCss                                                        StaticResource        lightning-component-tests\test\default\staticresources\lts_mochaCss.resource
Add    lts_mochaCss                                                        StaticResource        lightning-component-tests\test\default\staticresources\lts_mochaCss.resource-meta.xml
Add    lts_mochaJs                                                         StaticResource        lightning-component-tests\test\default\staticresources\lts_mochaJs.resource
Add    lts_mochaJs                                                         StaticResource        lightning-component-tests\test\default\staticresources\lts_mochaJs.resource-meta.xml
Add    lts_sinon                                                           StaticResource        lightning-component-tests\test\default\staticresources\lts_sinon.resource
Add    lts_sinon                                                           StaticResource        lightning-component-tests\test\default\staticresources\lts_sinon.resource-meta.xml
Add    lts_testutil                                                        StaticResource        lightning-component-tests\test\default\staticresources\lts_testutil.resource
Add    lts_testutil                                                        StaticResource        lightning-component-tests\test\default\staticresources\lts_testutil.resource-meta.xml
Add    mochaExampleTests                                                   StaticResource        lightning-component-tests\test\default\staticresources\mochaExampleTests.resource
Add    mochaExampleTests                                                   StaticResource        lightning-component-tests\test\default\staticresources\mochaExampleTests.resource-meta.xml
2019-02-15T16:06:23.159Z cli flushing stdout
2019-02-15T16:06:23.173Z sfdx:analytics using C:\Users\{user}\AppData\Local\sfdx\analytics.log for usage error logging
2019-02-15T16:06:23.413Z sfdx:analytics spawned usage "C:\Users\{user}\AppData\Local\sfdx\client\bin\node.exe C:\Users\{user}\AppData\Local\sfdx\client\dist\processes\logUsage"

The Salesforce CLI team launched the source:deploy and source:retrieve commands in Beta in winter 19. After collecting your feedback we have realized that the overlap between the mdapi and source deploy and retrieve commands is causing confusion about what commands should be used with which workflow (org development or package development). Due to this feedback, we are proposing the following changes:

The Proposal

Overall:

There will only be 2 sets of commands that move source to and from orgs:

• source:push, source:pull - these commands will track changes between the local project and the org

• mdapi:deploy, mdapi:retrieve - these commands will allow for fine-grained or bulk manipulation of source

Both sets of commands will default to maintaining the source file folder layout (i.e. source format), with an option to override the default for deploy and retrieve if you want to work in the older project file format (i.e. mdapi format).

Push and pull will work in source tracked orgs, and deploy and retrieve in all orgs

Other changes:

• We are going to add the additional selectivity options to mdapi:deploy/retrieve that are currently available on source:deploy/retrieve and then deprecate source:deploy/retrieve.

• mdapi:convert will be moved under the force:project topic and likely renamed to project:import. We will also add the additional selectivity options available for source:deploy/retrieve.

• source:convert will be moved under the force:project topic and likely renamed to project:export. We will also add the additional selectivity options available for source:deploy/retrieve.

• The mdapi:delete command with selectivity options will be implemented.

Is your feature request related to a problem? Please describe.
When I execute a mdapi:retrieve command for single package and unpackaged with a package.xml file that specifies a metadata component that does not exist in my org, I get no warnings.

I use the following command for retrieve:

$ sfdx force:mdapi:retrieve \
  --verbose \
  --singlepackage \
  --unpackaged package.xml \
  --retrieve retrieved \
  --wait -1 \
  --loglevel warn \
  -u alan

With the --verbose flag I see a list of all components retrieved but it does not display any warnings about components that were not retrieved.

What are you trying to do
I would like to see a warning for any components that were not retreived, so that I can fix my package.xml file, if there is a typo, or create the component in my org, if it is missing.

Describe the solution you'd like
mdapi:retrieve should display warnings when components specified in package.xml were not retrieved from the org.

Describe alternatives you've considered
When using Ant Migration Tool, to retreive the same package.xml I will get warnings displayed in the output:

[sf:retrieve] Retrieve warnings (1):
[sf:retrieve] package.xml - Entity of type 'ApexClass' named 'FooBar' cannot be found

Summary

VS Code reports that SFDX: Set a Default Orgsuccessfully ran even though the underlying sfdx force:config:set command failed and the default org was not able to be set.

Steps To Reproduce:

1. You must have at least two orgs in your environment. For example: org1 and org2
2. Set org1 to be the default org in your VS Code workspace
3. Find the *.json file that contains the info for org2 in your ~/.sfdx directory and clobber the accessCode and refreshToken values.
4. Click on the org1 button at the bottom of the VS Code window. When the org list dropdown appears, select org2 to be your new default org.

Expected result:

VS Code notifies the user that an error has occurred during SFDX: Set a Default Org

Actual result:

An error occurs when VS Code runs the sfdx force:config:set defaultusername=org2 command, but VS Code still outputs a success message for the command.

Additional information

VS Code Version:
45.1.0

Currently, it is not possible to set the following package settings via SFDX:

• apiAccessLevel
• postInstallClass
• setupWebLink

What are you trying to do
We're trying to have a seamless packaging & release process via CI.

Describe the solution you'd like
force:source:convert has a --packagename parameter which allows us to set the element in package.xml. I'd like to see additional parameters to allow us to specify values for the settings listed above.

Describe alternatives you've considered
The only workable options we have right now are hackish workarounds:

• Manually maintain a package.xml file with postInstallClass etc. set
• Use an XML editing tool in our CI process to insert the missing package setting elements into package.xml.

Summary

Short summary of what is going on or to provide context.

mdapi convert command fails when source has lightning web component bundle

I ran into the same issue reported by Mohith via Salesforce stack exchange.

Created the issue here so we can track it. This is a blocker for any teams to use LWC.

Steps To Reproduce:

1. Create an unmanaged package in Developer Edition org with lwc bundle and retrieve src by package name or clone the git repo here https://github.com/msrivastav13/mdapi-convert-lwc-bug.git

2. sfdx force:mdapi:convert -r ./mdapiout -d force-app

Expected result

Conversion should be performed successfully

Actual result

The error in the console is as below

An error was encountered processing path: /mdapio ut/src/lwc//.html.

Feel free to attach a screenshot.

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/6.52.2-c6cdc99881

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

OS and version:
Any

Summary

Failure to retrieve valid metadata, if it contains characters deemed invalid by the XML parser.

Steps To Reproduce:

1. Create a community
   1. Name: 😂
2. sfdx force:source:pull -f

Expected result

Retrieved the metadata for this in /sites

Actual result

Retrieval fails with:

ERROR: Invalid character (�) in string: 😂 Profile at index 0.

Additional information

Error: Invalid character (�) in string: 😂 Profile at index 0
    at XMLStringifier.module.exports.XMLStringifier.assertLegalChar («···»\node_modules\sfdx-cli\node_modules\salesforce-alm\node_modules\xmlbuilder\lib\XMLStringifier.js:149:15)
⁞

This is related to oozcitak/xmlbuilder-js#154 which got adopted in Leonidas-from-XIV/node-xml2js#395 therefore salesforce-alm would just need to bump its xml2js dependency (please).

SFDX CLI Version:
sfdx-cli/6.53.0 (windows-x64) node-v11.10.0

SFDX plugin Version:
salesforcedx 45.2.0 (core)

OS and version:

Caption        : Microsoft Windows 10 Pro
OSArchitecture : 64-bit
Version        : 10.0.17134
UBR            : 590
ReleaseId      : 1803

Is your feature request related to a problem?
It is a feature. Consultants and other service providers that work with multiple customers need to switch between dev hubs.

What are you trying to do
Would like to have multiple projects and have the default dev hub saved inside the project similar to default scratch org.

Describe the solution you'd like
Store the dev hub on project file along to default scratch org.

Is your feature request related to a problem? Please describe.
I would like to use the force:source:deploy command to push to a production org, or to a sandbox but enforce unit test execution. I'm unable to find a way to do so now.

What are you trying to do
Use the force:source:deploy command to delivery minor changes to Production without having to convert all the source, strip out the thousands of pieces I don't want to push, manually trim the generated package.xml, and finally push with force:mdapi:deploy

Describe the solution you'd like
Adding in the --testlevel flag would allow this command to target Production orgs and let me do small pushes, often required pre-deployment to the source I'm trying to delivery with CI when there is a dependency that can't be pushed in the same package due to limitation with the deployment infrastructure dependency resolution/order of operations.

Describe alternatives you've considered
I convert to MDAPI format, then trim down the resulting output. Usually it requires deleting dozens of directories and trimming all but a small amount from the generated package.xml so it is scoped correctly.

I am not able to retrieve my LWC components from org to local on windows machine . I ran below commands but both failed

sfdx force:source:retrieve -m LightningComponentBundle

or

sfdx force:source:retrieve -m LightningComponentBundle:helloWorld

Summary

Attempting to deploy report using force:source:deploy -x package.xml

Steps To Reproduce:

1. Create a report folder MyReportFolder
2. Create a simple report MyReport and save under MyReportFolder
3. Create a package.xml file that includes the following content:

<types>
    <members>MyReportFolder/MyReport</members>
    <name>Report</name>
</types>

4. Run sfdx command:

sfdx force:source:deploy -x package.xml

Expected result

Report should be created/updated in target instance

Actual result

The following error message is returned:

The ReportFolder named MyReportFolder/MyReport was not found in the workspace.

Additional information

Replacing the forward-slash in the report path with a backward-slash fixes the problem, as in:

<types>
    <members>MyReportFolder\MyReport</members>
    <name>Report</name>
</types>

SFDX CLI Version:
(sfdx --version) sfdx-cli/6.48.0-bfccc40118 (windows-x64) node-v8.9.4
(sfdx force --version) v44.0

OS and version:
Windows 7 64-bit

Summary

I'm trying to retrieve matadata from sandbox using SFDX: Retrieve Source from Org and using package.xml. But I get error:
Error deploying or retrieving source: The file or directory that you tried to deploy or retrieve isn't in a package directory that's specified in your sfdx-project.json file. Add this location to your "packageDirectories" value, or deploy or retrieve a different file or directory. For details about sfdx-project.json, see: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm

I have a fresh project created by running SFDX: Create Project with Manifest

When I create a class in this project and retrieve it as single file, it works without issue.

Steps To Reproduce:

1. SFDX: Create Project with Manifest
2. connect a sandbox org
3. right-click on default generated package.xml and run SFDX: Retrieve Source from Org

Expected result

source metadata are retrieved in ./force-app folder

Actual result

Error deploying or retrieving source: The file or directory that you tried to deploy or retrieve isn't in a package directory that's specified in your sfdx-project.json file. Add this location to your "packageDirectories" value, or deploy or retrieve a different file or directory. For details about sfdx-project.json, see: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm

Additional information

my sfdx-project.json file:
{
"packageDirectories": [
{
"path": "force-app",
"default": true
}
],
"namespace": "",
"sfdcLoginUrl": "https://test.salesforce.com",
"sourceApiVersion": "45.0"
}

VS Code Version:
1.31.1

SFDX CLI Version:
sfdx-cli/6.53.0-67a9cbb60c (windows-x64) node-v8.9.4
Salesforce Extension Pack: 45.2.0

OS and version:
Windows 10 (64)

What are you trying to do
It would be nice to be able to specify a test suite name as part of deployment command that would be used to specify which tests should be executed as part of the deployment, as an alternative to the RunSpecifiedTests option.

For example, if I have apackage with manifest as follows:

package.xml

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
  <types>
    <members>Foo</members>
    <members>FooTest</members>
    <members>Bar</members>
    <members>BarTest</members>
    <name>ApexClass</name>
  </types>

  <types>
    <members>MyTestSuite</members>
    <name>ApexTestSuite</name>
  </types>
</Package>

And the test suite specifies the tests I want executed during deployment:

MyTestsuite.testSuite

<?xml version="1.0" encoding="UTF-8"?>
<ApexTestSuite xmlns="http://soap.sforce.com/2006/04/metadata">
    <testClassName>FooTest</testClassName>
    <testClassName>BarTest</testClassName>
</ApexTestSuite>

Describe the solution you'd like
I would like to use a test level named RunTestSuite for example, that would require a test suite name be specified, possibily by reusing --runtests or with another flag. With this test level I don't have to explicitly list all my test classes I want to have run during deployment. Instead the tool would extract the list of tests from the test suite and run those.

Example:

$ sfdx force:mdapi:deploy \
  --testlevel RunTestSuite \
  --runtests MyTestSuite \
  --deploydir mypackage \
  --wait -1 \
  -u alan

# Maybe also supports multiple test suites:
$ sfdx force:mdapi:deploy \
  --testlevel RunTestSuite \
  --runtests MyTestSuite1,MyTestSuite2,MyTestSuiteN \
  --deploydir mypackage \
  --wait -1 \
  -u alan

When a user tries to deploy metadata that has git merge conflict markets in it, we simply return an error like:

Because this is a known format of strings and we are encoraging users to use source tracking, we could do a much better job of handling this special case.

For example, when using the git CLI if you try to commit file changes that have unresolved conflicts git will say something like "you are trying to commit files with unresolved conflicts, are you sure?".

We should do something similar and show a better error. "You are trying to deploy metadata to your org that has unresolved git conflicts. Please resolve the conflicts before you deploy."

Hello,

I have a scratch org create script that does a few things including data import.

What I have noticed: The first time I push changes from VS Code to the newly created scratch org, VS Code does a full push. Even if I changed only one file, I get the whole source push which takes quite some time.

In summary, I wait once for a complete push in my script and then have to wait for another full push in VS Code.

Is this behaviour to be expected?

Summary

I create a scratch org, then enable Communities, create a community, then try sfdx force:source:pull through the CLI or the VSCode command palette. It results in the following Error:

ERROR: Metadata API received improper input. Please ensure file name and capitalization is correct. Load of metadata from db failed for metadata of type:AppMenu and file name:AppSwitcher.

Steps To Reproduce:

1. create a scratch org
2. enable Communities
3. create a community
4. try sfdx force:source:pull through the CLI or the VSCode command palette
5. get error

Expected result

No error and to pull the changes from the scratch org

Actual result

Error ERROR: Metadata API received improper input. Please ensure file name and capitalization is correct. Load of metadata from db failed for metadata of type:AppMenu and file name:AppSwitcher.

Additional information

VS Code Version:
Version 1.32.0-insider (1.32.0-insider)

SFDX CLI Version:
sfdx-cli/6.53.0-67a9cbb60c (darwin-x64) node-v8.9.4

OS and version:
macOS Mojavie
10.14.3

Summary
"ERROR: Cannot read property 'fileName' of undefined." when trying to retrieve source from Org.

Steps To Reproduce:
Authorize a Sandbox Org
Right click package.xml and choose "Retrieve Source from Org"
Expected result
Source retrieved.

Actual result
ERROR: Cannot read property 'fileName' of undefined.

Is your feature request related to a problem? Please describe.
Having to change the working directory is a pain every time you want to push / pull. It would also make scripting cli usages a lot easier by optionally specifying the project directory.

Describe the solution you'd like
A flag --projectdirectory that would allow pushing and pulling from a directory that isn't the CWD.

Summary

I am receiving the error:
ERROR: Cannot read property 'fileName' of undefined.

Steps To Reproduce:

1. Define this package.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>AuraDefinitionBundle</name>
    </types>
    <version>45.0</version>
</Package>

2. Run this command:
   sfdx force:source:retrieve --manifest c:\_hilton\BossReno\manifest\package.xml

Expected result

The source should be retrieved

Actual result

ERROR: Cannot read property 'fileName' of undefined.

Additional information

The development environment is Salesforce Spring 2019

I have posted these questions on the forums:
https://salesforce.stackexchange.com/questions/251431/sfdx-error-cannot-read-property-filename-of-undefined/251569#251569

https://developer.salesforce.com/forums/ForumsMain?id=9062I000000QuEcQAK

All other nodes in the package.xml are working fine. Only the AuraDefinitionBundle is not working. I figured this out through process of elimination.

Here is my full package.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>ApexClass</name>
    </types>
    <types>
        <members>*</members>
        <name>ApexComponent</name>
    </types>
    <types>
        <members>*</members>
        <name>ApexPage</name>
    </types>
    <types>
        <members>*</members>
        <name>ApexTestSuite</name>
    </types>
    <types>
        <members>*</members>
        <name>ApexTrigger</name>
    </types>
    <types>
        <members>*</members>
        <name>AuraDefinitionBundle</name>
    </types>
    <types>
        <members>*</members>
        <name>StaticResource</name>
    </types>
    <version>45.0</version>
</Package>

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/6.54.4-c01dcc69db (windows-x64) node-v8.9.4

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

@salesforce/plugin-generator 1.0.1 (core)
@salesforce/sfdx-trust 2.0.1 (core)
builtins 1.0.0 (core)
salesforcedx 45.3.4

OS and version:
Windows 10 Pro

Summary

The force:project:create command fails when I attempt to use the --template standard flag

Steps To Reproduce:

1. Run the command sfdx force:project:create -n myProject --template standard

Expected result

A project is created with the new project scaffold described in the v. 45.3.1 release notes

Actual result

No project is created and the following error is returned:

'ERR_ASSERTION': Trying to copy from a source that does not exist: /Users/walkej/.local/share/sfdx/client/node_modules/force-language-services/dist/project/templates/.gitignore

Additional information

SFDX CLI Version:
sfdx-cli/6.54.4-c01dcc69db (darwin-x64) node-v8.9.4

SFDX plugin Version:
45.3.4

OS and version:
macOS 10.13.6 (17G5019)

Following up on Twitter thread.

Running VS Code 1.30.2 on Windows 7 with all manner of corporate security and proxies running. All examples below executed in VSC integrated terminal using Bash (installed via MINGW/Git Bash, not WSL).

$ sfdx -v
sfdx-cli/6.50.0-9817aece8a (windows-x64) node-v8.9.4

I am using the pre-release version but pinned to API 44.

$ time sfdx --version
sfdx-cli/6.50.0-9817aece8a (windows-x64) node-v8.9.4

real    0m3.729s
user    0m0.015s
sys     0m0.031s

$ time sfdx force:org:list
WARNING: apiVersion configuration overridden at 44.0
=== Orgs
     ALIAS         USERNAME                      ORG ID              CONNECTED STATUS
───  ────────────  ────────────────────────────  ──────────────────  ────────────────
                   [email protected]         00D36000000YDboEAG  ENOENT
                   [email protected]          00D1I000002yJUJUA2  invalid_grant
                   [email protected]   00D6A000002I66oUAC  invalid_grant
                   [email protected]   00Df4000003lKwxEAE  ENOTFOUND
                   [email protected]     00DB0000000Y0oEMAS  Connected
(D)                [email protected]               00D36000000YDboEAG  Connected
     DevHub        [email protected]    00D1N000002cKIQUA2  invalid_grant
     Prod_Deploy   [email protected]  00D1U000000t6NvUAI  ENOENT
     newhub        [email protected]   00D0b000000DNDpEAO  ENOTFOUND
     reports-test  [email protected]           00D36000000YDboEAG  ENOENT

No active scratch orgs found. Specify --all to see all scratch orgs

real    0m16.785s
user    0m0.000s
sys     0m0.047s

I do have a lot of trial orgs registered here from before Dev Hub became available on Developer Editions. I removed all orgs with sfdx force:auth:logout -p -a and reran the time test:

$ time sfdx force:org:list
WARNING: apiVersion configuration overridden at 44.0
ERROR:  No orgs can be found.

Try this:
Use one of the commands in force:auth or force:org:create to add or create new scratch orgs.

real    0m12.437s
user    0m0.000s
sys     0m0.077s

Opening an org:

$ time sfdx force:org:open -u [email protected]
WARNING: apiVersion configuration overridden at 44.0
Access org 00D36000000YDboEAG as user [email protected] with the following URL: https://david-ktema-dev-ed.my.salesforce.com/secur/frontdoor.jsp?sid=00D36000000YDbo!ARMAQPE7Xnq8.QeUSziUj3HXa3a8nnnExXwDwtGWd.LmoKLuFtH1wlkx_Pe9SJ3KPFSvhn2wAPOspLpdQNFLXO1MjvI52ppi

real    0m20.423s
user    0m0.000s
sys     0m0.078s

Happy to gather more timing and logging data if that is helpful.

Is your feature request related to a problem? Please describe.
I need to get the packageId when executing the following command.
sfdx force:package:version:report -p "myPackage" --json
or
sfdx force:package:version:report -p "04t50000000AbcD" --json

What are you trying to do
I want to get the package id from a specific attribute called packageId. Currently the Id is available on the message, but there is no easy way to extract it.

Describe the solution you'd like
I want to execute sfdx force:package:version:report -p "myPackage" --json or sfdx force:package:version:report -p "04t50000000AbcD" --json and I want to have an easy way to get the ID from the response.

Current return:
{"message":"The Subscriber Package Version Id 04t50000000AbcD is invalid, ...

Expected result:
{"packageId":"04t50000000AbcD","message":"The Subscriber Package Version Id 04t50000000AbcD is invalid, ...

Describe alternatives you've considered
A poor alternative would be extract it from specific parts to the current response or by reading the sfdx-project.json file to get the ID.

Summary

Changes made on default fields of custom quick actions in the source code are able to be pushed to a scratch org however, the opposite is not true. On-the-fly updates on pre-existing custom actions are not tracked by sfdx, ending up with No results found.

Steps To Reproduce:

1. Create a new Email Quick Action for any Object (my example: Lead)
2. Add some default fields. E.g. htmlBody, textBody, Subject ...
3. Optional: Add it to any page layout just to help you test the change
4. Pull your code (sfdx force:source:pull): This will create a file like Object.QuickActionName.quickAction-meta.xml
5. Make local changes in this file
6. Push it (sfdx force:source:push). Your changes will be reflected on your box
7. Make changes in your scratch-org (I've tested adding new default values for other fields and changing the value for existing ones)
8. Pull your code again and see: No Results Found
9. Repeat the process locally and push - Confirm that your changes made declaratively are gone

Expected result

It should detect declarative changes.

Actual result

It does not detect changes when pulling.

Additional information

Feel free to attach a screenshot.

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/6.53.0-67a9cbb60c (darwin-x64) node-v8.9.4

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core):
@salesforce/plugin-generator 1.0.1 (core)
@salesforce/sfdx-trust 2.0.1 (core)
builtins 1.0.0 (core)
salesforcedx 45.0.12 (pre-release)

OS and version:
MacOS High Sierra

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

sfdx plugins:update is not upgrading the custom plugin to the latest plugin

What is the expected behavior?

It should update to the latest version. See attachment.

Current sfdx version:

$ sfdx version
sfdx-cli/6.42.0-ae478b3cb8 (windows-x64) node-v8.9.4

When doing a source:retrieve of files that are already local, git detects these files as changed on even when there is no change. This was reported on windows so I suspect it is something to do with line endings.

Summary

sfdx plugins
command takes excessive time to run on my work computer

Steps To Reproduce:

1. open command prompt
2. sfdx plugins

Expected result

prompt return of plugins information to confirm version as described here: https://trailhead.salesforce.com/content/learn/projects/quick-start-lightning-web-components/set-up-salesforce-dx

Actual result

timed it at 2 minutes on work computer (personal computer does not have this issue)

Additional information

SFDX CLI Version:
6.34.0

OS and version:
windows 7 (I know, it's my work computer, not my choice here)

Summary

Given an object Project__c with a master-detail relationship to Account (relationship field name Account__c), with a local project tree and scratch org in sync with one another:

Make a local change to the file Project__c.object, such as changing the label of the Name field.

Issue

$ sfdx force:source:push

Receive in response

PROJECT PATH ERROR
───────────────────────────────────────────────────────────────────
force-app/main/default/objects/Project__c/Project__c.object-meta.xml Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field

Note that the sharingModel is set to ControlledByParent and the master-detail relationship field is present both in the source tree and in the scratch org - it's just not being pushed in this operation because that field is not changed.

SFDX CLI Version: confirmed in 6.50.0 and 6.51.1 (linux-x64) node-v10.15.0

OS and version: GalliumOS (Ubuntu derivative) 16.04

Summary

When deploying to an org with the force:mdapi:deploy command, if I cancel the deployment from inside the org then the CLI reports that as a successful deployment.

Steps To Reproduce:

1. Deploy some source via force:mdapi:deploy and use the -w xx flag to wait for results.
2. While the deploy is still running go into the org and cancel the deployment
3. Check the exit code returned by SFDX it should return a status code "0" while also reporting "Status: Canceled"

Run the same steps for a deployment that fails for whatever reason (e.g. test code fails) and it returns a status code "1"

Expected result

Cancelled deployments should be considered a failed deployment and return a non-zero status code.

Actual result

Cancelled deployments are considered successful deployments and return a zero status code

Additional information

This is a particular issue in our CI system that when a deployment is cancelled it considers the run to be successful so we have incorrect tracking for what was deployed or not.

SFDX CLI Version:
sfdx-cli/6.53.0-67a9cbb60c (windows-x64) node-v8.9.4

SFDX plugin Version:
@salesforce/plugin-generator 1.0.1 (core)
@salesforce/sfdx-trust 2.0.1 (core)
builtins 1.0.0 (core)
salesforcedx 45.2.0 (core)

OS and version:
Windows 10 Pro, 1709

Summary

Short summary of what is going on or to provide context.

Steps To Reproduce:

1. This is step 1.
2. This is step 2. All steps should start with '1.'

Expected result

Describe what should have happened.

Actual result

Describe what actually happened instead.

Additional information

Feel free to attach a screenshot.

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):

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

OS and version:

Summary

Fails to deploy using force:source:deploy when the package manifest contains a single CustomLabel.

Steps To Reproduce:

1. Create a package manifest with single CustomLabel, manifest/package.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">

 <types>
   <members>FOO_BAR</members>
   <name>CustomLabel</members>
 </types>

 <version>45.0</version>
</Package>

2. Add CustomLabel to workspace, force-app/main/default/labels/CustomLabels.labels-meta.xml:

<?xml version="1.0" encoding="UTF-8"?>
<CustomLabels xmlns="http://soap.sforce.com/2006/04/metadata">
    <labels>
        <fullName>FOO_BAR</fullName>
        <language>en_US</language>
        <protected>false</protected>
        <shortDescription>Foobar label</shortDescription>
        <value>FooBar</value>
    </labels>
</CustomLabels>

3. Deploy

  sfdx force:source:deploy -x manifest/package.xml

Expected result

The CustomLabel should have been deployed to the target org.
This is currently possible with Ant Migration Tool.

Actual result

ERROR: The CustomLabel named FOO_BAR was not found in the workspace.

Additional information

Changing the package manifest to use the CustomLabels type instead of CustomLabel works but this is deploying more than I want to push to the sandbox.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">

  <types>
    <members>*</members>
    <name>CustomLabels</members>
  </types>

  <version>45.0</version>
</Package>

SFDX CLI Version: sfdx-cli/6.54.4-c01dcc69db (linux-x64) node-v8.9.4

SFDX plugin Version:
@salesforce/plugin-generator 1.0.1 (core)
@salesforce/sfdx-trust 2.0.1 (core)
builtins 1.0.0 (core)
dependencies-cli 1.0.1
salesforcedx 45.3.4 (core)

OS and version: Ubuntu 16.04.5 LTS

Summary

I would say every sfdx command takes about 20 sec before it starts doing anything

Steps To Reproduce:

1. sfdx force:org:open -u upfsc

Expected result

immediate reaction and browser open

Actual result

cli starting run +0ms
cli checking autoupdater +562ms
rwlockfile read C:\Users\mhumpolec002\AppData\Local\sfdx\update.lock +0ms
cli-engine:hooks init C:\Users\mhumpolec002\AppData\Local\sfdx\client\dist\hooks\plugins\migrate.js +0ms
sfdx:hook:init:plugins:migrate enter +0ms
sfdx:plugins:migrate no v5 plugins need migration +0ms
sfdx:hook:init:plugins:migrate exit +4ms
cli dispatcher +1s
cli-engine:hooks plugins:parse C:\Users\mhumpolec002\AppData\Local\sfdx\client\dist\hooks\plugins\convertFromV5.js +33s
sfdx:hook:plugins:parse:legacy enter +0ms
sfdx:hook:plugins:parse:legacy exit +2ms
cli-engine:hooks plugins:parse C:\Users\mhumpolec002\AppData\Local\sfdx\client\dist\hooks\plugins\convertFromV5.js +74ms
sfdx:hook:plugins:parse:legacy enter +58ms
sfdx:hook:plugins:parse:legacy exit +1ms
cli-engine:hooks prerun C:\Users\mhumpolec002\AppData\Local\sfdx\client\dist\hooks\logAnalytics.js +24ms
sfdx:hook:analytics enter +0ms
sfdx:analytics setting up exit handler +0ms
sfdx:hook:analytics exit +2ms
cli running flow command { _version: '9.0.7' } +32s

Additional information

Windows 10 machine with ton of corporate security on top of it

SFDX CLI Version:
sfdx-cli/6.50.0-9817aece8a (windows-x64) node-v8.9.4

OS and version:
Windows 10 Enterprise, 64bit

Is your feature request related to a problem? Please describe.
We are unable to deploy zip files that contain a single package as there is no --singlepackage flag.

$ sfdx force:mdapi:deploy -c -f build/src-package.zip -u alan -w -1
Deploying /home/alan/repos/salesforce/build/src-package.zip...

Deployment finished in 1000ms

=== Result
Status: Failed
jobid: 0Afc000001XMXCxCAP
Completed: 2018-08-23T22:16:08.000Z
Component errors: 0
Components checked: 0
Components total: 0
Tests errors: 0
Tests completed: 0
Tests total: 0
Check only: true

=== Component Failures [1]
TYPE FILE NAME PROBLEM
───── ────────────────── ─────────── ────────────────────
Error labels/package.xml package.xml No package.xml found

ERROR: The metadata deploy operation failed.

The Ant Migration Tool provides the single package parameter that can be used with the sf:deploy target.

singlePackage - Optional. Defaults to false. Declares that the zipFile or deployRoot parameter points to a directory structure with a single package, as opposed to a set of packages.

– Ant Migration Tool Guide : Deploying Changes to a Salesforce Org

Another scenario where this is a problem, is when we retrieve a package using sfdx force:mdapi:retrieve --singlepackage, the zip file retrieved is not deployable using sfdx force:mdapi:deploy due to missing flag. This breaks symmetry of these commands.

What are you trying to do
We are currently using a mix of Ant Migration Tool and sfdx. The zip files we create as part of our build process are single package zip files, these are currently deployable using ant, however, we are unable to deploy the same zip file with sfdx due to missing flag. Having this flag available would really help us to transition away from ant and use sfdx.

Describe the solution you'd like
Add support for the --singlepackage flag to the sfdx force:mdapi:deploy command, so that it is possible to deploy zip package in this format and also add symmetry between sfdx force:mdapi:deploy and sfdx force:mdapi:retrieve

Describe alternatives you've considered
As a work around, we can unzip the single package and use the --deploydir flag for deploy but this is cumbersome.

Is your feature request related to a problem? Please describe.
Working in a DX project is done in most cases, on a specific feature , with a clear entry point (VisualForce page , Lightning app or any other URL).

Describe the solution you'd like
I would like to have a parameter like : defaultpath in the project level CLI Runtime Configuration
similar to FORCE_OPEN_URL from Environment Variables

What will be the result of the addition
The expected behaviour is to be able to set a parameter like any other parameter (ex. defaultusername in sfdx-config.json in the .sfdx foler ) that will be the --path .
Run open comment sfdx force:org:open will be open with defaultusername and defaultpath (as path)

Summary

Trying to pull Reports down from a Dev Sandbox (i.e., non Scratch org) with the command

sfdx force:source retrieve -m Report

gives no results returned, when there are definitely reports in the Org. No package.xml used in this scenario and I've been made aware that the metadata API doesn't support wildcarding for reports, which could be a factor here.

Steps To Reproduce:

1. Targetting a non-Scratch org which contains reports, run the sfdx command indicated above

Expected result

Report metadata is retrieved from the Org

Actual result

Message - No Results Returned

Additional information

Feel free to attach a screenshot.

SFDX CLI Version:

sfdx-cli/6.49.0-8edc6e0f5d (windows-x64) node-v8.9.4

Summary

Short summary of what is going on or to provide context.

Steps To Reproduce:

1. Go to Command Pallete
2. Select Create Lightning Component

Expected result

Creation of a lightning component

Actual result

Received the following error in the terminal:

sfdx force:lightning:component:create --componentname MicrobiltReportViewer --outputdir src\aura
! this.log is not a function
sfdx force:lightning:component:create --componentname MicrobiltReportViewer --outputdir src\aura ended with exit code 1

Additional information

Feel free to attach a screenshot.

VS Code Version:
1.28.2

SFDX CLI Version:
6.38.0-0d66175ccf

OS and version:
Windows 10

Summary

When I use the sfdx force:org:list command, I always get an error:
-- (node:51109) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 value listeners added. Use emitter.setMaxListeners() to increase limit

Steps To Reproduce:

1. sfdx force:org:list

Expected result

List all the org infos.

Actual result

got an error.
Error information: (node:51109) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 value listeners added. Use emitter.setMaxListeners() to increase limit

Additional information

sfdx force:alias:list command works correctly.

SFDX CLI Version: sfdx-cli/6.52.2-c6cdc99881 (darwin-x64) node-v8.9.4

OS and version: masOS Mojave 10.14.2

When issuing a command sfdx force:source:status -u <alias> or sfdx force:org:open -u alias against a scratch org that is expired it will return raw HTML to stdout/stderr. If you add the --json flag the response is a a little better as its in json format but the message is still raw html.

I think it would be better to provide an actual message that the org is expired rather than an html page that says the data can't be found.

$ sfdx force:org:open -u <alias>
ERROR:





<!-- ...................................................................................................
       ...................................................................................................
       ...................................................................................................
       ................................................................................................... -->


<div style="display:none;" id="errorTitle">Data Not Available</div>
<div style="display:none;" id="errorDesc">The data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our <A href="null" title="support (New Window)">support</a> page.</div>
<table cellspacing=10>
<tr><td><span style="font-weight: bold; font-size: 12pt;">Data Not Available</span></td></tr>
<tr><td>
The data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our <A href="null" title="support (New Window)">support</a> page.
<br><br>
Error ID: 398126296-244522 (-657220938)
</td>
</tr>
<tr><td>
<br clear="all"><br><br>


</td></tr>
</table>

</td></tr>
</table>




<!-- Body events -->
<script type="text/javascript">function bodyOnLoad(){if(window.PreferenceBits){window.PreferenceBits.prototype.csrfToken="null";};}function bodyOnBeforeUnload(){}function bodyOnFocus(){}function bodyOnUnload(){}</script>

</body>
</

edit: my cli/node verisons:

sfdx-cli/6.44.0 (windows-x64) node-v11.6.0

Summary

Deploy fails with a number of errors, summarised below:

• If Action is set to 'Tab', you must specify a CustomApplication.

To resolve this issue, I commented out profileActionOverrides for those profiles containing the node

Quite a few of these errors associated with apex classes occurred:

• An unexpected error occurred. Please include this ErrorId if you contact support: 470492228-1778 (976141748)

Another error associated with a trigger occurred:

An unexpected error occurred. Please include this ErrorId if you contact support: 470492228-1779 (841340242)

Another error associated with a ConnectedApp occurred:

• An unexpected error occurred. Please include this ErrorId if you contact support: 470492228-1780 (-147323903)

Steps To Reproduce:

1. Refresh my production org into a sandbox
2. Create a project with a manifest using the Salesforce Extensions for VSCode (45.2.0)
3. Copy current package.xml file into manifest folder
4. The package version is 44.0
5. Retrieve Source in Manifest from Source Org
6. Deploy Source in Manifest to Source Org

Expected result

I would expect a successful deploy to follow a successful retrieval if no further change has occurred in the files

Actual result

The deploy fails reporting 27 errors.

Additional information

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>ApexClass</name>
    </types>
    <types>
        <members>*</members>
        <name>ApexTrigger</name>
    </types>
    <types>
        <members>Envato_App</members>
        <name>CustomApplication</name>
    </types>
    <types>
        <members>*</members>
        <name>CustomMetadata</name>
    </types>
    <types>
        <members>*</members>
        <name>CustomObjectTranslation</name>
    </types>
    <types>
        <members>Coaching</members>
        <name>FlexiPage</name>
    </types>
    <types>
        <members>*</members>
        <name>Flow</name>
    </types>
    <types>
        <members>Account-Admin %28Account%29 Layout</members>
        <members>Account-Coaching %28Account%29 Layout</members>
        <members>Case-Coaching Interaction %28Case%29 Layout</members>
        <members>SystemSettings__c-System Settings Layout</members>
        <members>Account-Account Layout</members>
        <members>Case-Case Layout</members>
        <members>CaseClose-Close Case Layout</members>
        <members>CaseInteraction-Case Feed Layout</members>
        <members>Contact-Contact Layout</members>
        <members>Lead-Author Growth %28Lead%29 Layout</members>
        <members>Lead-Admin %28Lead%29 Layout</members>
        <members>Account-Author Growth %28Account%29 Layout</members>
        <members>Contact-Author Growth %28Contact%29 Layout</members>
        <members>Opportunity-Author Growth %28Opportunity%29 Layout</members>
        <members>Opportunity-Opportunity Layout</members>
        <name>Layout</name>
    </types>
    <types>
        <members>*</members>
        <name>Profile</name>
    </types>
    <types>
        <members>Account.NewCoachingInteraction</members>
        <members>Case.SendRichTextEmail</members>
        <name>QuickAction</name>
    </types>
    <types>
        <members>PhotoQC</members>
        <members>Datadog</members>
        <name>RemoteSiteSetting</name>
    </types>
    <types>
        <members>Account</members>
        <members>Case</members>
        <members>Opportunity</members>
        <name>Workflow</name>
    </types>
    <types>
        <members>Account</members>
        <members>Case</members>
        <name>Settings</name>
    </types>
    <types>
        <members>Account</members>
        <members>Case</members>
        <members>Contact</members>
        <members>SystemSettings__c</members>
        <members>Campaign</members>
        <members>Lead</members>
        <members>Opportunity</members>
        <members>JobExecutionLog__c</members>
        <name>CustomObject</name>
    </types>
    <types>
        <members>*</members>
        <name>Role</name>
    </types>
    <types>
        <members>AuthorManagementEmailTemplates</members>
        <members>AuthorGrowthEmailTemplates</members>
        <name>EmailTemplate</name>
    </types>
    <types>
        <members>*</members>
        <name>Group</name>
    </types>
    <types>
        <members>AuthorGrowthReports</members>
        <members>AuthorManagementReports</members>
        <name>Report</name>
    </types>
    <types>
        <members>AuthorGrowthDashboards</members>
        <members>AuthorManagementDashboards</members>
        <name>Dashboard</name>
    </types>
    <types>
        <members>*</members>
        <name>ApexPage</name>
    </types>
    <types>
        <members>*</members>
        <name>ConnectedApp</name>
    </types>
    <types>
        <members>ContentPipelineStages</members>
        <members>ContentCategories</members>
        <name>GlobalValueSet</name>
    </types>
    <version>44.0</version>
</Package>

VS Code Version:
1.30.2 (1.30.2)

SFDX CLI Version:
45.2.0

OS and version:
MacOS Sierra 10.12.6

Is your feature request related to a problem? Please describe.
I want to be able to leverage the new supertable functionality in cli-ux 5.0.0, in a plugin project that I'm working on, including sorting, filtering and outputting CSV files.

Describe the solution you'd like
Update the cli-ux dependency to 5.0.0.

Describe alternatives you've considered
Updating the dependency at the plugin level.

Additional context
None

Summary

Can't deploy class to sandbox using force:source:deploy

Steps To Reproduce:

1. Right click in source
2. Choose SFDX: Deploy This Source to Org

Expected result

Source is deployed to org.

Actual result

sfdx force:source:deploy --sourcepath r:\src\SFCI\src\classes\FeatureAccessHandler_Test.cls
ERROR: The "path" argument must be of type string. Received type undefined.
sfdx force:source:deploy --sourcepath r:\src\SFCI\src\classes\FeatureAccessHandler_Test.cls ended with exit code 1

VS Code Version:
1.28.2

SFDX CLI Version:
sfdx-cli/6.38.0 (windows-x64) node-v11.1.0

OS and version:
Windows 10

Summary

Just followed trailhead instructions of installing packages. All the necessary packages are installed. But running a create command does not results in an error.

Steps To Reproduce:

1. Using command palette call SFDX: Create Project.
2. Enter Project name and select folder.

Expected result

Project should get created.

Actual result

Getting an error that says : "SFDX: Create Project failed to run."

Additional information

This is the output:

Starting SFDX: Create Project

20:39:09.270 sfdx force:project:create --projectname HelloWorldLightningWebComponent --outputdir d:\SalesforceDX
! 'ENOENT': ENOENT: no such file or directory, uv_chdir
20:39:12.54 sfdx force:project:create --projectname HelloWorldLightningWebComponent --outputdir d:\SalesforceDX ended with exit code 1

VS Code Version: 1.31.1

SFDX CLI Version: 45.2.0

OS and version: Windows 10.