Repository navigation
fix(lora): preserve profile defaults and report selector errors - #837
Merged
Merged
Conversation
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.
Profiles can declare a served LoRA alias separately from its source, such as
lora: legalandlora_id: org/legal. Resolve those defaults through the selected profile's declarations while preserving the served selector. Explicit request selections, including null for the base model, override defaults. Both defaults and caller selections now require an actual declaration in that profile; aruntime.loravalue cannot authorize a source declared only by another profile.Request aliases still require exact agreement, and legacy
lora_idremains source-only. Decisions and System One gateway errors now identify the invalid or conflicting selector inerror.paraminstead of always naminglora_adapter.Follow-up to #830, correcting findings raised on #829. No SDK, adapter, model catalog, or dependency changes.
Validation:
Summary by CodeRabbit
New Features
Bug Fixes