-
Notifications
You must be signed in to change notification settings - Fork 25.6k
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
[s2s] fix --gpus clarg collision #6358
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6358 +/- ##
==========================================
+ Coverage 78.20% 78.38% +0.17%
==========================================
Files 148 148
Lines 27196 27196
==========================================
+ Hits 21269 21317 +48
+ Misses 5927 5879 -48
Continue to review full report at Codecov.
|
This is the issue I opened about it: #6310 it's more than just |
which other ones besides |
Anything else that is defined both in With your PR nothing collides at the moment. If we go into the direction of each module (and the base) defining its own args, most likely On the other hand, copying the same common args to every module is less than optimal. If transformers support Additionally, we can make any of these args optional like it was done recently with #6149, so if the arg is not there, it will not fail if the example doesn't support it. |
I don't understand exactly what you're proposing I don't think. This is just meant to fix a bug. |
I'm trying to communicate that currently adding new args is difficult because they are scattered in various places. It's not easy to tell when to put them in This PR duplicated a cl arg Replacing
|
Problem
finetune.py adds all the default pl args with this line
and all the generic args from
add_generic_args
.Solution
This moves the overlapping arg from lightning_base.py to the 2 pl examples that need it.
CC @stas00 @patil-suraj