Skip to content

Conversation

@bastimeyer
Copy link
Member

Logging extremely verbose data like HLS playlist contents for example doesn't really fit on the trace log level. Adding an ultimate verbosity log level makes more sense here, so we can add log calls to the HLS parser and similar things.

Is the name "all" fine? I've just renamed it from "paranoid" before submitting this PR, because I wasn't really happy with that name. "all" is the opposite of "none", which is at the other end of the log level list, and it's easier to remember, too.

Since there are two custom log levels now, I had to refactor a bit of code in order to prevent duplicate stuff and duplicate tests.

Copy link
Member

@gravyboat gravyboat left a comment

Choose a reason for hiding this comment

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

Typically I would expect this to be at the trace level but as you noted it's even more verbose than what might be seen there so I'm fine with calling it all even though it's non-standard (who really cares as long as we get the info). I'm going to mark this as approved @bastimeyer and you can merge it whenever.

@back-to back-to merged commit 2bf6ee4 into streamlink:master Nov 12, 2022
@bastimeyer bastimeyer deleted the logger/level-all branch November 12, 2022 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants