-
-
Notifications
You must be signed in to change notification settings - Fork 11k
fix(proxy): stop team BYOK model name corruption on model edit #29731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The condition
incoming != db_model.model_nameis designed to catch the case where the dashboard echoes back the internal routing key (before the read-path fix). After the read-path fix is deployed, the dashboard will instead send the public name (e.g."team-claude-sonnet"), which is always!=the internal key"model_name_{team_id}_{uuid}". The guard therefore never fires on the new client and falls through to return the incoming public name. This is still safe because_update_existing_team_model_assignmentlater detectsold_public_name == public_model_nameand skips the ACL update, then always setspatch_data.model_name = Noneat line 685.However, there is no test that covers this scenario end-to-end (UI sends public name on a non-rename edit), so the correctness of the combined path relies solely on a reader tracing through two functions.