Check if logging to file somehow got lost

[bep]

No description provided.

[jmooring]

So, we have a lot of related options, and it's not clear to me how some of these interact with each other.

--debug       debug output
--log         enable logging
--logFile     log filepath (if set, logging enabled automatically)
--verbose     verbose output
--verboseLog  verbose logging

And there's #9648.

[bep]

So, we have a lot of related options, and it's not clear to me how some of these interact with each other.

I was hoping that you could clarify this situation. I have no clue. The goal of the CLI rewrite was to not break anything, which is why I marked this as a bug... But I have never used file logging myself. Of the flags you list I would probably keep:

--verbose (= log level INFO)
--debug ( = log level DEBUG)

Which tells me that we could probably hide the above and add a new ... --logLevel.

And do logging to stdout only.

[jmooring]

I was hoping that you could clarify this situation. I have no clue.

Neither do I. Probably seemed like a good idea at the time.

---

Assuming --logLevel DEBUG includes both DEBUG and INFO statements, your suggestion works for me.

This reduces the number of flags from 5 to 1. If someone needs a file they can redirect to whatever.

probably hide the above

Or throw deprecation warnings.

[bep]

We also have the related --quiet which removes ... everything. But that is also muting non-log print statements (e.g. "Total in ...").

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.