Skip to content
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

Keyword arguments {'add_prefix_space': False} not recognized. #8322

Closed
rabeehkarimimahabadi opened this issue Nov 5, 2020 · 8 comments · Fixed by #8329
Closed

Keyword arguments {'add_prefix_space': False} not recognized. #8322

rabeehkarimimahabadi opened this issue Nov 5, 2020 · 8 comments · Fixed by #8329

Comments

@rabeehkarimimahabadi
Copy link

Hi
I am getting this message when running finetune_trainer.py on TPUs any idea how to remove it? thanks

@LysandreJik
Copy link
Member

Hi @rabeehkarimimahabadi. Could you please respect the issue template when opening issues? It is necessary for us to help you, otherwise we'll have to ask again and again for you to provide more information.

Please complete the issue template with the information related to your environment, to the command you launched, and the full error with the stack trace. Thanks.

@rabeehkarimimahabadi
Copy link
Author

rabeehkarimimahabadi commented Nov 5, 2020 via email

@LysandreJik
Copy link
Member

Since you're using the T5 model I believe you can safely ignore that warning, which is useful only for the byte-level BPE tokenizers (think GPT-2, RoBERTa).

Maybe @patil-suraj or @sshleifer know why such a warning is thrown when using T5 with the Seq2SeqTrainer

@sshleifer
Copy link
Contributor

Yeah it's happening in seq2seq dataset, you can safely ignore. Fixed in #8329

@rabeehkarimimahabadi
Copy link
Author

rabeehkarimimahabadi commented Nov 5, 2020 via email

@LysandreJik
Copy link
Member

Yes, the fix has just been merged.

@rabeehkarimimahabadi
Copy link
Author

Hi there, this is not fixed for me. and still I am getting it with running T5 using finetune_trainer.

@LysandreJik
Copy link
Member

Have you pulled from master to get the updated version?

In any case, as I've said before, this is a warning and not an error. You can safely ignore it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants