Repository navigation
fix(swarm): stop rejecting lane models against stale inherited providers - #143
Merged
Merged
Conversation
Use runtime provider resolution when validating lane defaults, so an in-lanes model override is not rejected against the coordinator's unrelated provider. Cover the check and serialized lane setup paths. Co-authored-by: EvoAgent <evo@ruiqilei.com>
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.
Why
Selecting gpt-6-astra@openai-oauth for the coordinator caused lanes configured with DeepSeek-V4-Pro to fail validation against the inherited openai-oauth provider, even though runtime resolution selected traex correctly.
Change
Use the existing runtime provider-resolution rule in lane validation. Add regressions for inherited-provider overrides, bare lane flags, and serialized lane setup forms.
Verification
This PR contains only the original targeted fix; mandatory qualified model identity will be handled separately.
Co-authored-by: EvoAgent evo@ruiqilei.com