Add --no-progress option for collect progress display suppression#132
Open
Redteam-LongwaveSpa wants to merge 1 commit into
Open
Add --no-progress option for collect progress display suppression#132Redteam-LongwaveSpa wants to merge 1 commit into
Redteam-LongwaveSpa wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
I am part of the RedTeam division of the company Longwave S.p.A. based in Italy.
For our activities we require logging each and every command with its relative output for every tool we use and noticed that DonPAPI, since it leverages rich.progress.Progress, outputs a progress bar which gets re-rendered each frame/update. This basically floods our logs.
Rather than opening an issue, given that it'd be a new feature anyway, we are proposing a new
--no-progressflag to suppress the rich.progress.Progress output (and only that).I added the arg definition as part of the
collect_subparserand also handled the case in which users might want to load an older recover file that does not have theno_progresskey/value saved.Thank you for your time and for the effort you put into developing this tool
Stefano - Longwave RedTeam