You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just saw that rumqttc v. 0.24.1 was released on may 11th.
The last crates.io update is 0.24.0 from 6 months ago.
This means going through crates.io the latest release doesn't export disconnect properties for v5.
The text was updated successfully, but these errors were encountered:
We have stopped creating releases on GitHub, it seems like this was an unfortunate oversight from our side of creating a patch, we have deleted the same. Thanks for pointing it out. We will release the patched rumqttc on crates and let you know here.
@de-sh while at it, I patched a fork of rumqttc to also expose RecvTimeoutError in rumqttc/src/v5/mod.rs on reexporting some elements of the private client module. It's a very small patch but allows distinguishing between not having received a message in the specified timeframe, say because I don't want to block and the client being disconnected.
I can open a corresponding PR if desired.
EDIT: I went ahead and created one just in case : #906
Hey,
I just saw that rumqttc v. 0.24.1 was released on may 11th.
The last crates.io update is 0.24.0 from 6 months ago.
This means going through crates.io the latest release doesn't export disconnect properties for v5.
The text was updated successfully, but these errors were encountered: