fix: omit null optional fields from task result payloads - #2809
Merged
maxisbey merged 1 commit intoJun 10, 2026
Merged
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
maxisbey
approved these changes
Jun 10, 2026
Copy link
Copy Markdown
Contributor
|
thanks for the fix! |
Sorry, something went wrong.
2 tasks
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
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.
Summary
Fixes #2539.
Task result delivery was serializing completed task payloads with model_dump(by_alias=True), which preserved optional None fields as JSON null inside nested content blocks. This can make tasks/result responses fail clients that treat those fields as optional-but-not-null.
This updates the task result handler to dump payloads with mode="json" and exclude_none=True, matching the session serialization path, while still adding the required related-task metadata.
Tests