Skip to content

fix: include user-defined LLM families in _resolve_architectures - #2

Closed
Ricardo-M-L wants to merge 1 commit into
mainfrom
fix/user-defined-llm-families-resolve
Closed

fix: include user-defined LLM families in _resolve_architectures#2
Ricardo-M-L wants to merge 1 commit into
mainfrom
fix/user-defined-llm-families-resolve

Conversation

@Ricardo-M-L

Copy link
Copy Markdown
Owner

Summary

  • Fix _resolve_architectures in llm_family.py to include user-defined LLM families when resolving model architectures
  • Previously, custom-registered models with model_family pointing to a user-defined model would fail architecture resolution
  • Now combines both builtin and user-defined families in a dict lookup

Problem

When a user registers a custom LLM model and specifies model_family that references another user-defined model (not a builtin), the _resolve_architectures method would return None because it only looked up in BUILTIN_LLM_FAMILIES.

Solution

Build a combined dictionary of both builtin and user-defined families, then look up the model_family from that combined dictionary.

Test plan

  • Test custom model registration with model_family pointing to user-defined model
  • Verify architecture resolution works correctly

Generated with Claude Code

The _resolve_architectures method only looked up architectures from
BUILTIN_LLM_FAMILIES, which caused custom-registered models with a
model_family pointing to a user-defined model to fail architecture
resolution. Now combines both builtin and user-defined families.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Ricardo-M-L

Copy link
Copy Markdown
Owner Author

Closing — staging PR on my own fork; upstream is xorbitsai#4860.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant