-
Notifications
You must be signed in to change notification settings - Fork 75
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(deps): update rust crate zbus to v5 #234
base: main
Are you sure you want to change the base?
Conversation
I'm inclined to wait till 1.83, since zbus does not support 1.81 any longer |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Now that rust 1.83 has been released, is it time to do this upgrade? |
Could not compile this crate now. I got following error messages.
My dependencies:
See rust-lang/cargo#14059, I think we need to upgrade zbus. |
This PR contains the following updates:
4
->5
Release Notes
dbus2/zbus (zbus)
v5.0.0
: π zbus 5.0.0Compare Source
encoding and decoding.
proxy
macro respects visibility. This includes all types generated byproxy
. Unfortunatelythis means that the existing code will have to set the visiblity explicitly to
pub
if theywere relying on the generated proxy to be public.
DBUS_COOKIE_SHA1
auth mechanism. #β727sha1
crate as a dependency, which can be problematic for some users. #β543EXTERNAL
is not an option, you might as well just useANONYMOUS
.authentication mechanisms with one of them being no-authentication, this really makes sense
since we can just autodetect what authentication method to use for a specific socket type on a
specific platform. This also simplifies the handshake logic and will allow us to pipeline the
whole client-side handshake in the future, when we can drop the xdg-dbus-proxy workarounds. #β781
same type of arguments.
fdo
API.interface
now generates a trait, Signals, that provides the same signalmethods as user specifies but w/o the
SignalEmitter
argument (#β871). The macro also generates2 implementations of this trait for:
method.
SignalContext::emit
. Add a new method to SignalContext that allows emitting a signal fora given interface and singal name.
mechanism. We'll use this in a following commit to avoid an allocation.
should be used with it. The implementation can choose this based on the socket type and the
target platform.
be private.
SignalContext
toSignalEmitter
. Since now this emits signals, this is a moreappropriate name. We keep a deprecated
SignalContext
type alias as well as thesignal_context
attribute ofinterface
for not completely breaking the existing code.AuthMechanism
in the root asdeprecated.
the conversion to NonZeroU32 panics. #β946
the
Proxy
API.p2p
feature is enabled.serde_bytes
Cargo feature. This is just a proxy feature forzvariant
'sserde_bytes
feature. #β1052
blocking-api
tozbus
&zbus_macros
. When enabled, thezbus::blocking
module is available. When disabled,proxy
macro ignores the value of
gen_blocking
attribute and doesn't generate blocking proxy. Thisfeature is enabled by default.
camino
feature as proxy for zvariant feature of the same name.sha1
crate.futures-sink
.rand
now an optional dependency. It is only enabled ifp2p
feature is enabled. This meansthat
rand
dependency is dropped for typical users.blocking
module docs.Configuration
π Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.