-
-
Notifications
You must be signed in to change notification settings - Fork 113
zb: Log errors from GetAll method calll #1325
New issue
Have a question about this project? Sign 8000 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
Comments
Thanks for reporting this and providing all the details. There isn't much zbus can do here. zbus already provides the option to disable property caching so you can always directly get the properties and then have some of them as fallible. We added support for fallible properties a while back (15203c1). Would that not work? |
The issue really is that we have a usecase where we will dynamically start listening for property changes without actually getting the property. I think the main issue here is that it will just silently fail on the call to listen for property changes. Would it be an idea to maybe add something like Tokio did where you can optionally enable tracing logs? If I got an error log for this error it would have been immediately clear what was happening. |
We already have tracing and in fact we trace a lot. If all you're asking for is one more log message, I'm fine with that. |
I didn't know that zbus supported tracing that's very nice! I ran my tests again with tracing enabled and I don't see any Error logs. So yeah I think in this case the perfect solution would be if either the creation of the proxy or the stream gives an error. But just a simple Error log would have already saved me a few hours so it might save the next person that runs into it a few hours aswell. |
Should be an easy PR to provide? ;) |
Uh oh!
There was an error while loading. Please reload this page.
take the following example client
I was testing out some test dbus interfaces and discovered that when you have a daemon that exposes a few properties 4 in my case but 1 of these causes a dbus error when calling Get on that property. The above code will not show an error or do really anything at all. I was able to track down the issue using
dbus-monitor
where I noticed zbus will do a GetAll call which silently fails and causes the above code to stall forever without any error or notice.The text was updated successfully, but these errors were encountered: