Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • zbus zbus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • dbusdbus
  • zbuszbus
  • Issues
  • #289
Closed
Open
Issue created Nov 14, 2022 by Luca Bruno@lucabContributor

[zbus-3.4] Regression due to `ObjectServer` change of behavior

Our CI at https://github.com/coreos/zincati/pull/886 caught a regression when updating from zbus-3.3 to zbus-3.4. Client tests are now timing out when trying to call the server, which is implemented on top of zbus. From an out-of-band chat, this seems to be due to following change of behavior:

ObjectServer to only serve methods destined to its connection.

This seems to be an unintended side-effect of the way that the consumer does object-server setup: https://github.com/coreos/zincati/blob/3a4f579a357d4aff56cc6b9a8e512fd105b40564/src/dbus/mod.rs#L36-L54

Moving forward it seems that the following changes would be useful:

  • restore previous behavior, by allowing destination to not be checked if no well-known name is registered through the connection
  • add a ConnectionBuilder::name_with_flags() method, so that both name and behavior-flags can be specified, without the need to go through DBusProxy::request_name()
Assignee
Assign to
Time tracking