-
Notifications
You must be signed in to change notification settings - Fork 457
fix(deps): update rust crate zbus to v5 (v2) #1953
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
Conversation
Package Changes Through 5c37512There are 4 changes which include sql-js with patch, clipboard-manager with patch, sql with patch, fs-js with patch Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
|
f49095d to
b1a7fc0
Compare
a40bf81 to
1227359
Compare
1227359 to
5c37512
Compare
FabianLars
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
incompatible msrv
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
|
@FabianLars would this PR be acceptable if zbus' MSRV was lowered to 1.77? @thomaseizinger already provided the PR for that and I'll merge it, if that's the case. |
|
@zeenix Yes, absolutely! |
Merged and released. |
|
Awesome! thanks so much :) |
This PR contains the following updates:
4->5Release Notes
dbus2/zbus (zbus)
v5.0.0: π zbus 5.0.0Compare Source
encoding and decoding.
proxymacro respects visibility. This includes all types generated byproxy. Unfortunatelythis means that the existing code will have to set the visiblity explicitly to
pubif theywere relying on the generated proxy to be public.
DBUS_COOKIE_SHA1auth mechanism. #β727sha1crate as a dependency, which can be problematic for some users. #β543EXTERNALis 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.
fdoAPI.interfacenow generates a trait, Signals, that provides the same signalmethods as user specifies but w/o the
SignalEmitterargument (#β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.
SignalContexttoSignalEmitter. Since now this emits signals, this is a moreappropriate name. We keep a deprecated
SignalContexttype alias as well as thesignal_contextattribute ofinterfacefor not completely breaking the existing code.AuthMechanismin the root asdeprecated.
the conversion to NonZeroU32 panics. #β946
the
ProxyAPI.p2pfeature is enabled.serde_bytesCargo feature. This is just a proxy feature forzvariant'sserde_bytesfeature. #β1052
blocking-apitozbus&zbus_macros. When enabled, thezbus::blockingmodule is available. When disabled,proxymacro ignores the value of
gen_blockingattribute and doesn't generate blocking proxy. Thisfeature is enabled by default.
caminofeature as proxy for zvariant feature of the same name.sha1crate.futures-sink.randnow an optional dependency. It is only enabled ifp2pfeature is enabled. This meansthat
randdependency is dropped for typical users.blockingmodule docs.v4.4.0: π zbus 4.4.0Compare Source
heaplessfeature, which is just a proxy tozvariantfeature of the same name.v4.3.1: π zbus 4.3.1Compare Source
issue in xdg-dbus-proxy has already been fixed, it will take some time before the fix is
released and is widely available.
type. We might need to add an attribute to control this in the future, as this as this may not
always be what the user wants.
mdbook-tocfrom @βbadboy.two distinct concepts separate.
v4.3.0: π zbus 4.3.0Compare Source
interfacecan now generateproxyfor you. #β236object_server::ResponseDispatchNotifierserde::Deserializefor it.blocking::Connection::call_methoddocs.v4.2.2: π zbus 4.2.2Compare Source
methods by default. #β799
v4.2.1: π zbus 4.2.1Compare Source
c1aa5c7, where westarted to invalidate properties in every
PropertyChangedsignal. This is wrong anyway but italso meant zbus interfaces breaking against gio. #β765
assert!instead ofdebug_assert!.debug_assert!is removed in release builds, alongwith any values computed inside it. This meant that since the use of
debug_assert!incommit
7fc3ab7, the fdo interfaces weren't getting added fornodes for release profile. Let's use
assert!instead. #β764pipelining, hence we need to handle
NEGOTIATE_UNIX_FDcommand's response before sending outBEGINcommand andHellomethod call message.full message could be received at the end of the client handshake process.
v4.2.0: π zbus 4.2.0Compare Source
dbus_interfacenow provides aspawnattribute to control whether the method call handling is spawned as a task or not.
pre-authenticated socket. This could also be socket that doesn't need any authentication. #β590.
method have a default implementation that just uses the lower-level sibling methods. Implementers
can either override this method or the lower-level method, depending on the underlying socket
they're using.
communication. This can be used with
connection::Builder::authenticated_socketto create aconnection for in-process communication. #β591.
Hellomethod call to thebus. This reduces unnecessary round-trips & hence latencies. #β493
one mechanism to be set.
auth_mechansim. This is inpreparation for #β731, when we will remove this method entirely.
Return an error instead of an explicit panic if attempted, since it is not an internal invariant.
windows-gdbusfeature and associated hacks.Turns out that the reference D-Bus implementation supports autolaunch fine and we don't need
special support for gdbus binary. Hopefully, in the near future, busd will also support it. #β687
Interfacebeing unstable API. Also recommend what people should do whendbus_interfaceisn't enough.autolaunch addresses so there is no need to create an address with scopes.
CANCELcommandduring a handshake, the server must move on to the next handshake method available (if any).
client is unknown or invalid in the current context, we shouldn't completely error out but rather
send an error and continue as if nothing happened.
output.
v4.1.2: π zbus 4.1.2Compare Source
To go with zbus_macros 4.1.2. Other changes:
v4.1.1: π zbus 4.1.1Compare Source
The actual change is in zbus_macros 4.1.1.
v4.1.0: π zbus 4.1.0Compare Source
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.