fix: enhance message deserialization to prevent MESSAGE_COERCION_FAIL… #86
+894
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…URE (#85)
The issue occurred when messages were stored in LangChain's serialized format with 'lc', 'type', 'constructor' fields but not properly deserialized back to message objects, causing errors when the application expected objects with 'role' and 'content' attributes.
This fix ensures robust handling of message serialization/deserialization with proper error recovery and detailed logging for debugging.