-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Ensure user sets backend to local w/ quantization #3524
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
Conversation
The change LGTM. It looks like there's some failing test. @Infernaught can you take a look? |
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
This is very aggressive check that is already causing user-facing issues (#3529). I understand the motivation for raising an error if the user selects quantization and the Ray backend, but that's not what this is doing. This is raising an error if the user doesn't EXPLCITLY select the local backend, which is quite extreme. We should NEVER require user to specify the local backend explicitly if the local backend is going to be used anyway. Going to need to revert this and yank the v0.8.1 release. |
Previously: users could omit backend from their config when running LLM finetuning with quantization
Now: users are prompted to set backend to local explicitly when running LLM finetuning with quantization