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.

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

fix: Don't log the FmtSpan::ENTER event because it generates unnecessary logs #4387

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

Michael-F-Bryan
Copy link
Contributor

@Michael-F-Bryan Michael-F-Bryan commented Jan 4, 2024

It looks like @john-sharratt added the FmtSpan::ENTER event while debugging poll_oneoff in a7f4460, but it was never removed afterwards so it ended up in the 4.2.4 release.

We don't want to be logging FmtSpan::ENTER because it means any async function annotated with #[tracing::instrument] will emit a log message every time the future is polled. Considering each read from a socket will poll the future again, that means you can easily end up with tens of thousands of unnecessary log entries printed to the screen when running with RUST_LOG=wasmer_wasix=debug.

@Michael-F-Bryan Michael-F-Bryan changed the title fix: Don't log the FmtSpan::ENTER event because it generates unnece… fix: Don't log the FmtSpan::ENTER event because it generates unnecessary logs Jan 4, 2024
@Michael-F-Bryan Michael-F-Bryan merged commit 743bee2 into master Jan 4, 2024
51 of 52 checks passed
@Michael-F-Bryan Michael-F-Bryan deleted the remove-unnecessary-log-enter branch January 4, 2024 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants