-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MOD-4118: handle deserialization errors #2342
MOD-4118: handle deserialization errors #2342
Conversation
8803b51
to
0bbbf63
Compare
0bbbf63
to
f77a035
Compare
…ouldnt-terminate-entire-containers
input_id="in-xyz0", | ||
function_call_id="fc-123", | ||
input=api_pb2.FunctionInput( | ||
args=b"\x80\x04\x95(\x00\x00\x00\x00\x00\x00\x00\x8c\x17", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of a byte string here, can you feed it a pickled object? or is that impossible because it needs to be a different package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah would have to somehow pickle the object in another venv than it's being pickled in which sounds annoying but more realistic, but both of these causes serialization errors
…ouldnt-terminate-entire-containers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the test!
Moves deserialization for inputs to after constructor to ensure we handle user exceptions and don't retry them -- likely regression from #2081