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

Please revert the progress bar #289

Closed
AndrewRayCode opened this issue Jan 30, 2020 · 10 comments
Closed

Please revert the progress bar #289

AndrewRayCode opened this issue Jan 30, 2020 · 10 comments

Comments

@AndrewRayCode
Copy link

AndrewRayCode commented Jan 30, 2020

It looks like the progress bar has caused numerous issues, the most interrupting of which seems to be truncating or dropping output that developers rely on to get information back from SFDX. The "workaround" of adding --json is not human friendly so it is not a workaround. On top of that, the progress bar itself apparently doesn't report the correct progress.

These issues have been open for at least two weeks now and not addressed. Could you please revert it until the issues can be addressed?

@clairebianchi
Copy link
Collaborator

@AndrewRayCode see my comment in #271
We hope to have the change out next week

@AndrewRayCode
Copy link
Author

AndrewRayCode commented Feb 14, 2020

CC @clairebianchi @ntotten if we can help prioritize a revert, or if that's not an option, can we get some visibility into why this has blocked core functionality for five weeks now? Will there be a post mortem available for consumers of this library to understand how this issue has been ongoing for so long? I feel in the dark about understanding how this library is updated when there are critical issues. Could you also provide instructions for how to downgrade sfdx as a workaround until a fix is in place?

See
#274
#276
#271

Screen Shot 2020-02-13 at 5 59 53 PM

@ntotten
Copy link
Contributor

ntotten commented Feb 14, 2020

The fix for this was released two weeks back. You can see the info in the release notes: https://developer.salesforce.com/media/salesforce-cli/releasenotes.html

You can set an env variable SFDX_USE_PROGRESS_BAR=false to disable.

@AndrewRayCode
Copy link
Author

@ntotten that does not work, this appears to be still broken

Command we're running:

SFDX_USE_PROGRESS_BAR=false sfdx force:source:deploy -u OurEnvironment --testlevel RunLocalTests -x manifest/package.xml

Which has this output:

Screen Shot 2020-02-14 at 12 01 06 PM

It's the latest sfdx:

sfdx-cli: Updating CLI... already on latest version: 7.45.1-bc18d49798

And not sure if this is relevant:

Installing plugin salesforcedx... yarn add v1.21.1

Additionally, forcing end users to switch output type is not a fix, and is something sfdx itself should handle. All other cli tools like this detect TTY environments and don't add progress indicators that don't work in TTY environments automatically.

Again as this has been broken for so long it would be great to get more visibility into priority and understand how reverts / rollbacks happen

@clairebianchi
Copy link
Collaborator

@AndrewRayCode Do you have a specific version of salesforcedx plugin installed manually? You can check by running sfdx plugins. Can you please run sfdx plugins:uninstall salesforcedx and then run sfdx plugins --core?

We fixed the TTY environment issue, the progress bar should not show up for the TTY environment. The environment var is for teams that still wanted to see the old-style output in TTY environments. If you are seeing the progress bar in TTY environments then you are likely on an older version of the saelsforcedx plugin even if you have updated the Salesforce CLI.

@AndrewRayCode
Copy link
Author

This is in a system that on every run does:

wget https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz
(then installs)

and then does

sfdx update

and then does

sfdx plugins:install salesforcedx@latest

it fully updates on every run

@clairebianchi
Copy link
Collaborator

@AndrewRayCode can you send me the output of when you run sfdx plugins --core?

@amphro
Copy link
Contributor

amphro commented Feb 14, 2020

We made the fix to TTY here: oclif/cli-ux@9f57d7f however it looks like we might not be depending on that version in the toolbelt. Sorry for the confusion @AndrewRayCode - well get that updated by next Thursday.

I did verify that SFDX_USE_PROGRESS_BAR is in there though. After an npm install on salesforcedx@latest, I see:

node_modules/salesforce-alm/dist/lib/mdapi/mdapiDeployReportApi.js:        // if SFDX_USE_PROGRESS_BAR is true use progress bar, if not use old output
node_modules/salesforce-alm/dist/lib/mdapi/mdapiDeployReportApi.js:        this.useProgressBar = kit_1.env.getBoolean('SFDX_USE_PROGRESS_BAR', true);

Maybe there is a bug in there but it seems to work on my end. Any additional information would help.

On a side note, you don't need to run sfdx update OR the plugin:install. The wget is pointing to the most up-to-date archive which has salesforcedx bundled in it. It would probably save some time in your CI.

@sjurgis
Copy link

sjurgis commented Feb 28, 2020

This is the ridicilous output I get with progress bar disabled (iTerm/oh-my-zsh):

Screen Shot 2020-02-28 at 2 31 46 PM

@clairebianchi please reopen the ticket...

@ntotten
Copy link
Contributor

ntotten commented Feb 28, 2020

@sjurgis We aren't reverting the progress bar, the feedback has been overwhelmingly positive. Feel free to open a new issue explaining your problem.

@forcedotcom forcedotcom locked as resolved and limited conversation to collaborators Feb 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants