Repository navigation
Conversation
ShaanGS
requested review from
Pa04rth,
northdpole,
paoga87 and
robvanderveer
as code owners
November 10, 2026 15:23
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review: 1
Please check the settings in the CodeRabbit UI or the
|
This branch has not been 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.
Fixes #1218.
Google no longer serves the gemini-2.5 flash models to new API keys, so on staging the OIE noise filter, chat and the other helpers fail with a 404 for anyone setting up fresh. #1151 fixed the noise-filter default on main; this does the same on staging for every gemini-2.5-flash-lite and gemini-2.5-flash default in the app code,
.env.example, the README examples and the Module B runbook. They become gemini-3.5-flash-lite, which the API error suggests, and gemini-3.5-flash (the suggested 3.8-flash returned 503 for me).Left as they are:
gemini-2.5-prodefaults, until you say which model they should use (see the question on OIE on staging fails for new Gemini keys: the gemini-2.5 defaults are retired (follow-up to #1151) #1218)VERTEX_CHAT_MODEL, since I couldn't test VertexI ran the pipeline on staging with a new key: before this, Module B got a 404 on every batch and the run stopped there. With this branch and no overrides, it classifies the staged records. The unit tests give the same result as on staging.