Does ZBUS keep connections alive internally? Will it restart them if they exit?

[AmeliaRose802]

Hi ZBUS Team,
I got asked about retries on a PR comment and realized I didn't know the answer so I'd better ask :)

If the connection gets terminated for whatever reason, will the crate restart it?

Bonus question:

Are any of the ZBUS errors returned during the set up process retriable? I think .build() might return retriable errors based on this comment:

/// Fails if the journald socket couldn't be opened.

However, I'm not sure which enum variants this function returns.

Thanks so much for your help!

[zeenix]

If the connection gets terminated for whatever reason, will the crate restart it?

No. You'll get an error immediately (e.g from reading a MessageStream or any signal stream, or in sending a message etc) and you can retry. However, if you're talking to the bus itself, the chances of connection getting lost is close to none. If the bus process goes down or restarts, you've bigger problems anyway and you (or zbus) doesn't know if reconnection could possibly work.

Are any of the ZBUS errors returned during the set up process retriable?

That would depend entirely on the error. It's super hard to answer in a generic way.

I think .build() might return retriable errors based on this comment:

/// Fails if the journald socket couldn't be opened.

Where do you see this doc comment? I can't find it anywhere in our repo's log. Anyway, the error sounds like not something you can just retry. The socket wouldn't magically start to exist (or have the needed permission) a few microseconds or seconds later.

---

Its zbus btw (all lower-case). :)

[AmeliaRose802]

Thanks for your answer! And sorry about the caps!

[zeenix]

And sorry about the caps!

Np. You're not the first or the last one to make that mistake. 😂

[zeenix]

Oh and if you're tackling dbus broker restarts, I've a plan up handle that well in busd: dbus2/busd#138 .