Conversation
github-actions
bot
added
bug
seratch
force-pushed
the
fix/materialize-input-history-iterables
branch
from
c00633d to
7ce0368
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request fixes conversation-history replay paths that could preserve Pydantic
ValidatorIteratorobjects in input items. When users persisted and reloadedto_input_list()history (for example with custom Redis workflows), validated payloads could retain iterator-backed fields and become difficult to serialize or inspect. The change updatesItemHelpers.input_to_new_input_listto normalize list inputs through_to_dump_compatible, ensuring nested iterable fields are materialized into JSON-friendly structures before reuse. Tests were updated to cover the validated-input scenario and assert the resulting payload is dump-compatible.