Skip to content
This repository has been archived by the owner on May 11, 2023. It is now read-only.

Lower or drop the spamming-debug for cached properties #300

Open
zeenix opened this issue Nov 15, 2022 · 1 comment
Open

Lower or drop the spamming-debug for cached properties #300

zeenix opened this issue Nov 15, 2022 · 1 comment

Comments

@zeenix
Copy link
Collaborator

zeenix commented Nov 15, 2022

In GitLab by @elmarco on Nov 15, 2022, 13:33

My RUST_LOG=debug is flooded with worrying messages like:
2022-11-15T12:30:17.022824Z DEBUG zbus::abstractions::async_channel: Error receiving: receiving from an empty and closed channel

It should be silent for cached properties, or reduced to a much lower level (even trace would be too loud imho - and since it's not an error, it should not say so)

@zeenix
Copy link
Collaborator Author

zeenix commented Nov 15, 2022

even trace would be too loud imho - and since it's not an error, it should not say so)

trace is supposed to be super verbose IMO but sure, maybe we should both.

It should be silent for cached properties

Right but the channel doesn't know about its user/caller and IMO it should stay that way. Maybe add a boolean setting on it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant