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

Fix progress bars not working #594

Merged
merged 2 commits into from
Sep 30, 2022
Merged

Fix progress bars not working #594

merged 2 commits into from
Sep 30, 2022

Conversation

rickardgranberg
Copy link
Contributor

This is a suggested fix for issue #593

I decided to rename the flag to --no-progress to match the one in the bench command

@@ -82,7 +82,7 @@ NOTE: This is an experimental feature.
put.Flag("name", "Override the name supplied to the object store").StringVar(&c.overrideName)
put.Flag("description", "Sets an optional description for the object").StringVar(&c.description)
put.Flag("header", "Adds headers to the object").Short('H').StringsVar(&c.hdrs)
put.Flag("progress", "Disables progress bars").Default("true").BoolVar(&c.noProgress)
put.Flag("no-progress", "Disable progress bars").UnNegatableBoolVar(&c.noProgress)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since the new cli library now have negatable booleans I think I'd rather like:

put.Flag("progress", "Disable progress bars").Default("true").BoolVar(&c.progress)

like in stream backup and restore, its a bit more in tune also with how we handle other boolean flags now

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Update coming!

@ripienaar ripienaar merged commit 5ac644e into nats-io:main Sep 30, 2022
@ripienaar
Copy link
Collaborator

nice one thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants