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 ran into an issue with @therriault where remote workers had Blosc, but the Client didn't. This resulted in un-decompressible data being shipped to the client.
I was surprised that this occured because he was after 2.23 where the handshake was implemented. My guess is that serialization functions are using blosc outside of the normal compression channels and don't have the handshake information.
The text was updated successfully, but these errors were encountered:
I ran into an issue with @therriault where remote workers had Blosc, but the Client didn't. This resulted in un-decompressible data being shipped to the client.
I was surprised that this occured because he was after 2.23 where the handshake was implemented. My guess is that serialization functions are using blosc outside of the normal compression channels and don't have the handshake information.
The text was updated successfully, but these errors were encountered: