question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature Request: Control how verbose output is

See original GitHub issue

As described in https://groups.google.com/forum/#!searchin/got-your-back/verbose|sort:date/got-your-back/50TDppD3-5E/971Z6SwtFwAJ, it would be helpful to have optionally quieter output.

Full steps to reproduce the issue:

  1. Run GYB (especially as a cron job)
  2. See many lines showing all updates

Expected outcome (what are you trying to do?): I’d like to optionally see less output. I’d think that a numeric --verbose=<#> argument would cover what I’m thinking of. The levels that occur to me are:

  1. Silent except for fatal errors
  2. Warnings but no other information
  3. Everything from lower levels and statistics on completion of a step but not status messages during the step
  4. Everything from lower levels and status messages during the step (this is the current output)
  5. Everything from lower levels and the current output from --debug

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:2
  • Comments:10 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
scelfocommented, Aug 13, 2021

Hi, any chance this could be picked up again? From the comments it sounds like the pull request is very close.

1reaction
jay0leecommented, Jul 3, 2020

Sorry it’s taken me forever to take a look. In general it looks good. rewrite_line() was an attempt by me to let GYB “say” more while taking less space. However it clearly made a mess for scheduled jobs and it’s probably outlived it’s usefulness. I suggest we try just doing away with it and making all of those calls just call logging at an appropriate level instead.

Also, what was the reasoning behind making DEBUG the default level and logging most informative messages under that instead of INFO?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Developers - Feature Request: Control how verbose output is -
Expected outcome (what are you trying to do?): I'd like to optionally see less output. I'd think that a numeric --verbose=<#> argument would...
Read more >
Feature Request: command line control of output variable visibility ...
I'd like to control the verbosity of terraform in general, and output vars specifically (I'd also like some means of controlling the order...
Read more >
#PSTip Taking control of verbose and debug output, part 1
When working with cmdlets enabling verbose or debug output is easy: these commands have common switch parameters that can be used to do...
Read more >
Verbose output - HTTPie 3.2.1 (latest) docs
To see all the HTTP communication, i.e. the final request/response as well as any possible intermediary requests/responses, use the --all option. The ...
Read more >
Verbose Mode Options - Intel
Verbose Mode Options. The Diagnostics Utility for Intel® oneAPI Toolkits has six verbosity levels to add more detail in the output of each ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found