Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4
->4.2.0
Release Notes
dbus2/zbus (zbus)
v4.2.0
: 🔖 zbus 4.2.0Compare Source
dbus_interface
now provides aspawn
attribute 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_socket
to create aconnection for in-process communication. #591.
Hello
method 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-gdbus
feature 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
Interface
being unstable API. Also recommend what people should do whendbus_interface
isn't enough.autolaunch addresses so there is no need to create an address with scopes.
CANCEL
commandduring 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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.