Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@mateo-berri is attempting to deploy a commit to the Berri AI Team on Vercel. A member of the Team first needs to authorize it. |
4 of 6 tasks
This branch was successfully deployed
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.
TLDR
Documents how
service_tierreaches Vertex AI once BerriAI/litellm#34959 merges. That PR sends a Vertex tier as theX-Vertex-AI-LLM-Shared-Request-Typeheader, since Vertex answers 400 to theserviceTierbody fieldChanges
The Gemini page's
service_tiersection now has one table for whatgemini/andvertex_ai/each send for every value.autostays priority on the Gemini API and sends no tier on Vertex, and an unknown value such asscaleanswers 400 unlessdrop_paramsis set. The section also covers the Provisioned Throughput fallback of the header, the responseservice_tierthat Vertex now reports fromusageMetadata.trafficType, and Vertex batch rowsThe Vertex PayGo tutorial and the Vertex page now point at
service_tier, and theirtrafficTypetables listON_DEMAND_FLEX, which Vertex reports for Flex PayGoEach new behavior carries
<SinceVersion v="1.112.0" />, the first release planned to carry #34959. This PR should merge after #34959Checks
uv run --no-project --with pyyaml python3 scripts/check-docs.py docsprintedNo structural problems found.