-
Notifications
You must be signed in to change notification settings - Fork 132
Open
Description
Is it expected that a message deserialized from a pipe in thread 1 can be passed and safely read from thread 2? I'm running into an issue where attempting to inspect such an object hangs when accessed from thread 2. It only seems to happen when the object is ~64k or greater.
My workaround for now is to instead call .to_dict() on the message and pass that around instead, which works but is obviously not great.
If this is surprising behavior I can put together a reproduction.
Metadata
Metadata
Assignees
Labels
No labels