Zeeshan Ali Khan

Btw while I added a workaround for this in zbus 4.2.1, I wanted to point out that I wouldn't want to keep this workaround forever in zbus. I'm thinking ideally...

> If that's the case, then Flatpak apps that use zbus are unlikely to be runnable on older LTS distros (Debian, Ubuntu LTS, RHEL family, SLES family, etc.) because any...

> and hence backported Actually I'm not sure there is even backporting needed. At least Debian stable seems to already have xdg-dbus-proxy 0.1.4, ~~which is quite recent~~. If the coming...

> Interoperability requires some restraint on the embracing every latest cool idea that Lennart comes up with. I don't think this is new in sdbus. I think sdbus has been...

> 13% of a few microseconds is very much insignificant It's not **a few** microseconds even on high end machines. > in particular for a thing that happens once in...

I bumped into this today and spent the whole afternoon (instead of meeting cool folks at FOSDEM) to figure out why my tasks don't spawn. > Thanks for reporting this....

> The problem is not making the PR — it is coming to a decision about which of the options is best. Gotcha! Given that it's a pretty bad footgun...

> If we find anybody who still has a legitimate case for passing in a blocking socket I don't think anyone was asserting there is a use case for this....

> I'm concerned about breaking changes. That's fair. > It also introduces a runtime cost, because most sockets passed to `from_std` will already be in non-blocking mode Is that a...

We (me, @LiliC and @krnowak) discussed this further today and we had a question that will help us decide on how to proceed further with this issue: From what we...