Fix handling of text_message_outputs output structure in parallel translation example #1115
+3
−3
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.
Problem:
The code assumed
ItemHelpers.text_message_outputs()
returned a single string per result (e.g.,"Hola mundo"
), but it actually returns a list of strings (e.g.,["Hola", "Mundo"]
). This caused aTypeError
when joining outputs.Example of Failure:
Changes:
text_message_outputs(...)
with" ".join(...)
to safely flatten each agent’s output into a single string:Benefits:
TypeError
by ensuring all outputs are strings.This change ensures the parallel translation workflow works reliably, even when agent outputs vary in structure.