fix(examples): use canonical CMS asset URL for chat-with-image example#242
Merged
Conversation
The example pointed at the marketing site's Next.js image-optimizer proxy (mistral.ai/_next/image?url=...), which now returns 404. The API server cannot fetch it and rejects the request with 400 invalid_request_file (code 3310), failing the examples CI job. The underlying CMS asset is still available, so point directly at it and drop the fragile proxy wrapper.
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
2 participants
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.
The chat-with-image example used a
mistral.ai/_next/imageproxy URL that now returns 404, so the image can't be fetched and the example fails with a 400. Point at the image asset directly instead.