You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: CustomTextEmbedding lookup is case-sensitive after canonical model resolution #650
Custom models can be registered using one casing (for example Org/Model)
and later instantiated using another (org/model).
Although TextEmbedding resolves the model name case-insensitively, CustomTextEmbedding later retrieves the postprocessing configuration
using the original user-provided model name instead of the canonical
resolved model name.
This can result in a KeyError during construction.
What is the expected behaviour?
Once a model name has been resolved, all subsequent lookups should use the
canonical resolved model name so that model registration and instantiation
remain case-insensitive.
A minimal reproducible example
register_custom_model("Org/Model", ...)
TextEmbedding("org/model")
Current:
KeyError
Expected:
Construction succeeds.
What Python version are you on? e.g. python --version
Activity
joein commentedon Sep 16, 2026
Thanks for pointing it out and proposing a fix!
Closing this as the fix is available in main