-
Notifications
You must be signed in to change notification settings - Fork 28.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the config class comparison for remote code models #35592
Conversation
4c0d2ac
to
0bb5b32
Compare
cc @ArthurZucker for review! |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
gentle ping @ArthurZucker, and sorry for the spam! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks! 🤗 time to check if we had other brittle tests like this one!
…5592) * Fix the config class comparison when repeatedly saving and loading remote code models * once again you have committed your debug breakpoint
…5592) * Fix the config class comparison when repeatedly saving and loading remote code models * once again you have committed your debug breakpoint
…5592) * Fix the config class comparison when repeatedly saving and loading remote code models * once again you have committed your debug breakpoint
The config class comparison previously used
str(model_class.config_class)
, which resulted in mismatches because the actual class was loaded from a cache dir and therefore had the cache dir path as part of its full class name string.This new test just uses
model_class.__name__
which is much less error-prone.Fixes #35584, related to #29854