Insane log levels (1000s per second) since recent changes in master - PEBKAC alert ;)
Just a heads up for you devs in case this generates support issues - because I almost logged one until I figured it out just before I sent it.
As you're aware, there were a handful of changes to logging in recent commits. Previous config files had a setting in them which set log.level to 3. But they either weren't working, and the commits fixed that, or level 3 increased greatly in verbosity with the commits. I had a minor issue today and went I went to check /var/log/messages, I couldn't open the log, it crashed the log viewer, because my last few messages files had swollen to be gigabytes in size, which I found to be courtesy of pipewire issuing literally thousands of messages per second.
I tracked it down to that property being set, thus avoiding logging a support issue I thought might be a bug - but since an existing config file and new pipewire = crashing PC from giant logs, this might rear its head again with other users. Thought I'd mention it and hopefully save you some time trying to troubleshoot, if you hear of similar symptoms in the near future as others try the new code.
Hope this helps :)