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.

Sign up for GitHub

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

Jump to bottom

log spamming #91

Closed
lovasoa opened this issue Nov 19, 2023 · 0 comments · Fixed by #92
Closed

log spamming #91

lovasoa opened this issue Nov 19, 2023 · 0 comments · Fixed by #92

Comments

@lovasoa
Copy link
Contributor

lovasoa commented Nov 19, 2023

At debug level, this crate logs one line per byte of input, which makes the debug logs quite hard to read.

[2023-11-19T17:27:14Z DEBUG markdown::tokenizer] feed:    byte U+0020 to ParagraphInside
[2023-11-19T17:27:14Z DEBUG markdown::tokenizer] feed:    byte `s` (U+0073) to ParagraphInside
[2023-11-19T17:27:14Z DEBUG markdown::tokenizer] feed:    byte `e` (U+0065) to ParagraphInside
[2023-11-19T17:27:14Z DEBUG markdown::tokenizer] feed:    byte `c` (U+0063) to ParagraphInside
[2023-11-19T17:27:14Z DEBUG markdown::tokenizer] feed:    byte `r` (U+0072) to ParagraphInside
[2023-11-19T17:27:14Z DEBUG markdown::tokenizer] feed:    byte `e` (U+0065) to ParagraphInside

Maybe this log could be moved to TRACE level ?
@lovasoa lovasoa mentioned this issue Nov 19, 2023
Merged
wooorm pushed a commit that referenced this issue Nov 20, 2023
@lovasoa
Fix to use trace for verbose debug logs
8ea1401 
Closes GH-91.
Closes GH-92.

Reviewed-by: Titus Wormer <tituswormer@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix to use trace for verbose debug logs lovasoa/markdown-rs
1 participant
@lovasoa