-
Notifications
You must be signed in to change notification settings - Fork 12
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: function name 'requires_agumentation' to 'requires_augmentation' #118
fix: function name 'requires_agumentation' to 'requires_augmentation' #118
Conversation
…tation' Signed-off-by: Will Johnson <[email protected]>
Signed-off-by: Will Johnson <[email protected]>
Signed-off-by: Will Johnson <[email protected]>
Signed-off-by: Will Johnson <[email protected]>
Hi @willmj thanks for the change looks good. Although it might mean that if this merges then main repo will break correct? I beleive it will affect teh CI processes in the main repo, so we should merge both PRs together. And also if there is a future fms-acceleration release, we need to make a main repo release simultanously? I find this flow abit cumbersome and perhaps can be improved @anhuong BTW moe plugin is currently not default in image. this is due to dependency on a git repo with the kernels inside. Issue to copy the kernels over is #105 |
Hey Fabian - that's correct, and as long as we make the changes in both repos and do a fms-acceleration release before fms-hf-tuning, there shouldn't be any problems in the images either. |
PR #434 in fms-hf-tuning |
@willmj yea but we did run into that problem that any problems with image build is only caught in the fms-hf CI.. is that too late do you think? should we have a minimal image build CI in fms-accel? DId you test tha changes of both repos together yet? |
I just ran the tests in fms-hf-tuning and some are failing but seem to fail because of other changes not related to this one:
Tests are failing because of the wrong filepath, I will fix in the fms-hf-tuning PR I don't know if we need an image build for fms-acceleration, we can always limit a version in fms-hf-tuning if a problem arises though. |
With this commit all tests pass:
|
ok sounds good @willmj . I merge this PR and then you merge the fms-hf PR? |
Yes sounds good @fabianlim, although it needs to be approved again |
Nit fix for function name. Would require a change in
sft_trainer.py
as well if this is wanted.