Skip to content

fix(providers/amazon-bedrock): strip empty text content to avoid API errors#6255

Closed
MaxAller wants to merge 173 commits intovercel:mainfrom
MaxAller:fix/bedrock-empty-text-blocks
Closed

fix(providers/amazon-bedrock): strip empty text content to avoid API errors#6255
MaxAller wants to merge 173 commits intovercel:mainfrom
MaxAller:fix/bedrock-empty-text-blocks

Conversation

@MaxAller
Copy link
Copy Markdown
Contributor

@MaxAller MaxAller commented May 9, 2025

Background

Without this, with maxSteps set, we sometimes see messages sent to the API like this:

{
  role: 'assistant',
  content: [ { text: '\n\n' }, { toolUse: [Object] } ]
},

This leads to API errors like this:

The text field in the ContentBlock object at messages.7.content.0 is blank. Add text to the text field, and try again.

This happens often enough, maybe half the time in my experience, to cause a lot of pain on our side.

Summary

This change simply filters out this useless but apparently harmful message.

Verification

I've been running with this change locally for a day and haven't seen the issue recur, and nothing else seems to have obviously broken.

Tasks

  • Tests have been added / updated (for bug fixes / features)
  • [n/a] Documentation has been added / updated (for bug fixes / features)
  • A patch changeset for relevant packages has been added (for bug fixes / features - run pnpm changeset in the project root)
  • Formatting issues have been fixed (run pnpm prettier-fix in the project root)

Future Work

Related Issues

Fixes #6254.

dylanmoz and others added 30 commits April 3, 2025 08:10
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…nge (vercel#5531)

Co-authored-by: Carl Brugger <cebrugg@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…#5541)

Co-authored-by: Bram Meerten <bram.meerten@acagroup.be>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
)

Co-authored-by: Sam Denty <sam@samdenty.com>
Co-authored-by: Sam Denty <samddenty@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot and others added 20 commits April 30, 2025 16:09
## Background

This pull request adds the ability for clients to resume an ongoing chat
generation stream after a network disconnect.

## Summary

This pull request adds support for the `useChat` hook to resume an
ongoing chat generation stream by exposing `experimental_resume()` that
can be called by any client, typically during the initial mount of the
hook.

The `experimental_resume` function makes a `GET` request to the api
endpoint you've initialized the hook with (or `/api/chat` by default)
and streams the contents of the stream if it is active or fails silently
if it has ended.

In order for `experimental_resume` to work as intended, it requires the
usage of the
[`resumable-stream`](https://www.npmjs.com/package/resumable-stream)
package for stream creation and a redis instance for the package to
manage the pub/sub mechanism.

## Verification

An example has been added at `examples/next-openai/app/use-chat-resume`
to test the feature. Follow the following steps to test it end-to-end:
1. Run the development server
2. Navigate to `http://localhost:3000/use-chat-resume`
3. Send a message that will have a longer generation duration, example
"Write an essay about Michael Jordan"
4. Once the generation starts, click the chat id above to open the
conversation in a new tab
5. Verify the stream gets resumed

## Tasks

- [x] Tests have been added / updated (for bug fixes / features)
- [x] Documentation has been added / updated (for bug fixes / features)
- [x] A _patch_ changeset for relevant packages has been added
- [x] Formatting issues have been fixed (run `pnpm prettier-fix` in the
project root)

---------

Co-authored-by: Lars Grammel <lars.grammel@gmail.com>
# Releases
## ai@4.3.13

### Patch Changes

-   Updated dependencies [6c59ae7]
    -   @ai-sdk/ui-utils@1.2.10
    -   @ai-sdk/react@1.2.11

## @ai-sdk/react@1.2.11

### Patch Changes

-   6c59ae7: feat (ui/react): support resuming an ongoing stream
-   Updated dependencies [6c59ae7]
    -   @ai-sdk/ui-utils@1.2.10

## @ai-sdk/solid@1.2.12

### Patch Changes

-   Updated dependencies [6c59ae7]
    -   @ai-sdk/ui-utils@1.2.10

## @ai-sdk/svelte@2.1.11

### Patch Changes

-   Updated dependencies [6c59ae7]
    -   @ai-sdk/ui-utils@1.2.10

## @ai-sdk/ui-utils@1.2.10

### Patch Changes

-   6c59ae7: feat (ui/react): support resuming an ongoing stream

## @ai-sdk/valibot@0.1.25

### Patch Changes

-   ai@4.3.13

## @ai-sdk/vue@1.2.10

### Patch Changes

-   Updated dependencies [6c59ae7]
    -   @ai-sdk/ui-utils@1.2.10

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Background
This pull request fixes a docs formatting issue due to a missing comma
in useChat reference docs.

## Summary

Fixed formatting in useChat reference docs by adding a comma.

## Tasks
- [x] Documentation has been added / updated (for bug fixes / features)
- [x] Formatting issues have been fixed (run `pnpm prettier-fix` in the
project root)

## Related Issues
vercel#6052
## Background

The Dify provider allows developers to easily integrate Dify's
application workflow with their applications using the Vercel AI SDK.

## Summary

This PR adds the Dify provider documentation to the AI SDK, enabling
users to understand how to implement and use the Dify integration.

## Tasks

- [x] Documentation has been added for the Dify provider
- [x] Installation instructions are included
- [x] Usage examples for both cloud and self-hosted instances are
provided

## Related Issues

[Support Dify Provider](vercel#4084)

---------

Co-authored-by: Lars Grammel <lars.grammel@gmail.com>
<!--
Welcome to contributing to AI SDK! We're excited to see your changes.

We suggest you read the following contributing guide we've created
before submitting:

https://github.com/vercel/ai/blob/main/CONTRIBUTING.md
-->

## Background

<!-- Why was this change necessary? -->

## Summary

<!-- What did you change? -->

## Verification

<!--
For features & bugfixes.
Please explain how you *manually* verified that the change works
end-to-end as expected (independent of automated tests).
Remove the section if it's not needed (e.g. for docs).
-->

## Tasks

<!--
This task list is intended to help you keep track of what you need to
do.
Feel free to add tasks and remove unnecessary tasks as needed.

Please check if the PR fulfills the following requirements:
-->

- [ ] Tests have been added / updated (for bug fixes / features)
- [ ] Documentation has been added / updated (for bug fixes / features)
- [ ] A _patch_ changeset for relevant packages has been added (for bug
fixes / features - run `pnpm changeset` in the project root)
- [ ] Formatting issues have been fixed (run `pnpm prettier-fix` in the
project root)

## Future Work

<!--
Feel free to mention things not covered by this PR that can be done in
future PRs.
Remove the section if it's not needed.
 -->

## Related Issues

<!--
List related issues here, e.g. "Fixes vercel#1234".
Remove the section if it's not needed.
-->
## Background

The safetyRating was an empty object for some reason

## Summary

Fixes vercel#6109
…el#6133)

## Background

Before in issues like vercel#5499 &
vercel#5833, if users ran into an
issue where the messages array failed to parse correctly they'd run into
a difficult to debug error `Invalid prompt: messages must be an array of
CoreMessage or UIMessage`

## Summary

This PR extends these error messages to include more details on what
exactly went wrong, which is useful information for debugging when stuff
breaks.

On security: I think this is an okay change since the data sent is not
private
This adds gemini-2.5-pro-preview-05-06 to AI SDK
## Background

Laminar has updated its SDK and docs and added an example Next.js app.
This is needed to better guide AI SDK users

## Summary

A guide on Laminar as an observability provider is updated.
## Background

The below MCP SSE message will make the stream reader timeout.  
```
data: /message?sessionId=123\r\nevent: endpoint
```

## Summary

Fix the `splitLines` parser issue. The CRLF pointer was incorrectly
implemented.
# Releases
## ai@4.3.15

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/react@1.2.12
    -   @ai-sdk/ui-utils@1.2.11

## @ai-sdk/amazon-bedrock@2.2.9

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/anthropic@1.2.11

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/azure@1.3.23

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai@1.3.22

## @ai-sdk/cerebras@0.2.14

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai-compatible@0.2.14

## @ai-sdk/cohere@1.2.10

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/deepinfra@0.2.15

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai-compatible@0.2.14

## @ai-sdk/deepseek@0.2.14

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai-compatible@0.2.14

## @ai-sdk/elevenlabs@0.0.3

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/fal@0.1.11

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/fireworks@0.2.14

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai-compatible@0.2.14

## @ai-sdk/google@1.2.17

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/google-vertex@2.2.21

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/anthropic@1.2.11
    -   @ai-sdk/google@1.2.17

## @ai-sdk/groq@1.2.9

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/hume@0.0.2

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/lmnt@0.0.2

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/luma@0.1.8

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/mistral@1.2.8

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/openai@1.3.22

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/openai-compatible@0.2.14

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/perplexity@1.1.9

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/provider-utils@2.2.8

### Patch Changes

-   d87b9d1: fix(provider-utils): fix SSE parser bug (CRLF)

## @ai-sdk/react@1.2.12

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/ui-utils@1.2.11

## @ai-sdk/replicate@0.2.8

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/revai@0.0.2

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/solid@1.2.13

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/ui-utils@1.2.11

## @ai-sdk/svelte@2.1.12

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/ui-utils@1.2.11

## @ai-sdk/togetherai@0.2.14

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai-compatible@0.2.14

## @ai-sdk/ui-utils@1.2.11

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8

## @ai-sdk/valibot@0.1.27

### Patch Changes

-   ai@4.3.15

## @ai-sdk/vue@1.2.11

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/ui-utils@1.2.11

## @ai-sdk/xai@1.2.16

### Patch Changes

-   Updated dependencies [d87b9d1]
    -   @ai-sdk/provider-utils@2.2.8
    -   @ai-sdk/openai-compatible@0.2.14

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…ming stream (vercel#6224)

## Background

This pull request updates the documentation for the GET handler in the
resumable streams section to account for a race condition that may occur
when the stream ends in-flight.

## Summary

Updated the route by adding the code snippet that handles the above
condition.

## Tasks

- [x] Documentation has been added / updated (for bug fixes / features)
- [x] Formatting issues have been fixed (run `pnpm prettier-fix` in the
project root)

## Related Issues

vercel#6052
## Background

Bug with Vue that led to status not updating when tab was changed.

## Summary

Changes status from using SWR to using Vue ref.
# Releases
## @ai-sdk/vue@1.2.12

### Patch Changes

-   b54cb59: fix (ai-sdk/vue): fix status reactivity

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…errors.

Without this, with maxSteps set, we sometimes see messages sent to the API like this:

```
{
  role: 'assistant',
  content: [ { text: '\n\n' }, { toolUse: [Object] } ]
},
```

This leads to API errors like this:

```
The text field in the ContentBlock object at messages.$n.content.0 is blank. Add text to the text field, and try again.
```

This change simply filters out this useless but apparently harmful message.
switch (part.type) {
case 'text': {
// Skip empty text blocks
if (!part.text.trim()) {
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I am making the assumption here that this is sufficient for Bedrock's definition of "blank", but it seems reasonable enough to me.

@MaxAller MaxAller marked this pull request as ready for review May 9, 2025 21:59
@seannetlife
Copy link
Copy Markdown

thanks for this! i am going to use patch-package to get this in as i am desperate for the extended rates aws provides.

@rfsmart-eland
Copy link
Copy Markdown

Just trying to follow this as I'm hungry for the fix in my app.

How do we get this PR merged and deployed?

@lgrammel
Copy link
Copy Markdown
Collaborator

please rebase against latest main if this is still relevant for ai sdk 5

@MaxAller MaxAller closed this Jul 25, 2025
@MaxAller MaxAller deleted the fix/bedrock-empty-text-blocks branch July 25, 2025 16:52
lgrammel pushed a commit that referenced this pull request Aug 9, 2025
…errors (#7559)

## Summary

Without this, with maxSteps set, we sometimes see messages sent to the
API like this:

```
{
  role: 'assistant',
  content: [ { text: '\n\n' }, { toolUse: [Object] } ]
},
```

This leads to API errors like this:

```
The text field in the ContentBlock object at messages.$n.content.0 is blank. Add text to the text field, and try again.
```

This change simply filters out this useless but apparently harmful
message.

## Related Issues

Fixes #6254.

Supersedes #6255

---------

Co-authored-by: josh <josh@afterima.ge>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Amazon Bedrock + streamText + maxSteps often leads to APICallError