fix: add missing return in load_model_with_fallback#235
Closed
benaskins wants to merge 1 commit intowaybarrios:mainfrom
Closed
fix: add missing return in load_model_with_fallback#235benaskins wants to merge 1 commit intowaybarrios:mainfrom
benaskins wants to merge 1 commit intowaybarrios:mainfrom
Conversation
When mlx_lm.load() succeeds on the happy path (no ValueError), the function falls through to implicit return None instead of returning the loaded (model, tokenizer) tuple. This causes a TypeError in LLMModel.load(): TypeError: cannot unpack non-iterable NoneType object The bug only affects models that load successfully without needing the tokenizer or strict=False fallback paths (which do have return statements).
Author
|
Closing. Dup of PR #230 |
This was referenced Mar 31, 2026
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
1 participant
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.
When mlx_lm.load() succeeds on the happy path (no ValueError), the function falls through to implicit return None instead of returning the loaded (model, tokenizer) tuple.
This causes a TypeError in LLMModel.load():
TypeError: cannot unpack non-iterable NoneType object
The bug only affects models that load successfully without needing the tokenizer or strict=False fallback paths (which do have return statements).