| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Sorry, something went wrong.
|
This PR has been closed automatically. This repo only keeps pull requests open when they come from a maintainer, or from a contributor a maintainer has assigned to the linked issue, and you aren't currently assigned to #3467. If a maintainer assigns you to #3467, this PR reopens on its own and there's nothing more you need to do here. Assignment is a maintainer call based on capacity; comments that only ask to be assigned don't factor in. What does help is engaging on the issue itself by confirming the repro, explaining why it matters for your use case, or describing the approach you'd take. You're welcome to keep pushing commits here (just avoid force-pushing, since GitHub can't reopen a rewritten branch), but that on its own won't get the PR reviewed or the issue assigned, and realistically most auto-closed PRs stay closed. There's no need to open a new PR either way. CONTRIBUTING.md has the full reasoning, but in short:
Maintainers: reopen, remove missing-issue-link, or add bypass-issue-check to override. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #3467
Summary
FuncMetadata.convert_result validates CallToolResult.structured_content but returns the result unchanged. Plain model returns validate then model_dump/dump_python with by_alias=True, so wire keys match outputSchema. The CallToolResult path skipped that dump, so Python field names that pass validation (populate_by_name / by_name) could be emitted while outputSchema advertises aliases.
Motivation and Context
Clients validating structuredContent against the published outputSchema reject otherwise-valid tool results when aliases are used. This aligns the CallToolResult short-circuit with the plain-return path (#1073 / #1099). Distinct from #3100 / #3118 (schema generation mode).
How Has This Been Tested?
Breaking Changes
None intended. Wire output for CallToolResult tools that previously leaked Python field names will now use aliases (matching schema / plain returns).
Types of changes
Checklist
Additional context
Smallest fix: after validate_python(..., by_alias=True, by_name=True) on CallToolResult.structured_content, dump with by_alias=True and model_copy the normalized dict — same serialization as the plain-return path.
AI disclosure
This PR was prepared with AI assistance (Cursor / Grok): issue draft, repro, patch, and PR text. Changes were verified locally on current main (08a3bc8) with the new regression test and the full test_func_metadata.py file.