Skip to content

fix(ai): store raw invalid tool input as structured error object#14629

Open
Jim1874 wants to merge 2 commits intovercel:mainfrom
Jim1874:fix-parse-tool-call-invalid-input
Open

fix(ai): store raw invalid tool input as structured error object#14629
Jim1874 wants to merge 2 commits intovercel:mainfrom
Jim1874:fix-parse-tool-call-invalid-input

Conversation

@Jim1874
Copy link
Copy Markdown

@Jim1874 Jim1874 commented Apr 20, 2026

Fixes invalid JSON input being stored as raw string instead of structured error object.

Closes #14442

@tigent tigent Bot added ai/core core functions like generateText, streamText, etc. Provider utils, and provider spec. bug Something isn't working as documented labels Apr 20, 2026
Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional Suggestion:

Two inline test snapshots are incorrect after the { rawInvalidInput: toolCall.input } code change, causing test failures.

Fix on Vercel

@Jim1874 Jim1874 closed this Apr 22, 2026
@Jim1874 Jim1874 reopened this Apr 22, 2026
@Jim1874
Copy link
Copy Markdown
Author

Jim1874 commented Apr 22, 2026

Note: Vercel CI Authorization Required

All GitHub Actions CI checks (tests, lint, build) pass ✅.

The only failing check is Vercel Authorization (Authorization required to deploy). This is an account-level authorization issue — the Vercel GitHub App does not have permission to deploy from this fork.

This does not block PR merging. The PR is MERGEABLE. A maintainer with Vercel permissions can either:

  1. Approve the Vercel CI run manually, or
  2. Merge without Vercel CI (since all other checks pass)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai/core core functions like generateText, streamText, etc. Provider utils, and provider spec. bug Something isn't working as documented

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid tool call input stored as raw string causes API rejection on next step

1 participant