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

Log messages from bevy dependencies displayed as log instead of their name #13362

Open
Satellile opened this issue May 14, 2024 · 0 comments
Open
Labels
A-Diagnostics Logging, crash handling, error reporting and performance analysis C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong

Comments

@Satellile
Copy link

Bevy 0.13.1 // Windows 10

When I create an AudioBundle to play a sound, I get

[timestamp] INFO log: found the format marker [ff, fb] @ 0+2 bytes.
[timestamp] INFO log: using xing header for duration

printed in my log/console output. I'm creating Audiobundles often to play sounds, and it makes my log output very noisy; however, I couldn't suppress it using a filter and LogPlugin, as I didn't know the source of the log message.

The expected output would be

[timestamp] INFO symphonia_core::probe: found the format marker [ff, fb] @ 0+2 bytes.
[timestamp] INFO symphonia_bundle_mp3::demuxer: using xing header for duration

as in this case, symphonia is the source of the log message. Passing filter: "symphonia_core::probe=warn,symphonia_bundle_mp3::demuxer=warn".to_string(), as my LogPlugin filter still correctly filters out these log messages.

Similar behavior is observed for some other Bevy dependencies (e.g. log messages from naga are also showing up just as log)

Additional information

My Discord help thread: https://discord.com/channels/691052431525675048/1239685546972938381

Discord thread of someone else with the same issue: https://discord.com/channels/691052431525675048/1222256688527310958/1222256688527310958

@Satellile Satellile added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels May 14, 2024
@alice-i-cecile alice-i-cecile added A-Diagnostics Logging, crash handling, error reporting and performance analysis S-Needs-Investigation This issue requires detective work to figure out what's going wrong and removed S-Needs-Triage This issue needs to be labelled labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Diagnostics Logging, crash handling, error reporting and performance analysis C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong
Projects
None yet
Development

No branches or pull requests

2 participants