-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
TF GPT2: clearer model variable naming with @unpack_inputs #16311
Conversation
Some tests failed locally: One such test: |
The documentation is not available anymore as the PR was closed or merged. |
Hey @cakiki 👋 The problem you're seeing is related to another change that is happening at the same time -- we are refactoring the auto-regressive generation function, where the (see next comment) |
@sgugger @patrickvonplaten calling for your opinion here. TL;DR:
To fix it we have two options:
I'm pro option 2, but WDYT? |
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.
Other than the issue under discussion, looks solid 🔥
I'm in favor of 1). I haven't done a good job at reviewing the refactor PR I think - see: #15944 (comment). Backwards compatibility for models such as GPT2 is extremely important and people do use The other possibility is to deprecate |
Were there other models where we renamed |
Perhaps, going to check and open a PR to fix it (including this one) @cakiki I will fix the issue in a separate PR, and will ping you to rebase with |
@cakiki the fix is merged -- rebasing with |
(please rerun the tests locally before merging, and confirm here that they pass) |
Rebasing with
|
|
@gante I uninstalled tensorflow and explicitly pinned it >=2.5 and that worked. I noticed that
|
If it helps:
|
@cakiki It is settling on TF 2.3 because of python 3.6-related limitations on several packages :( We are actually having an internal discussion about potentially dropping support to python 3.6, since it is causing issues with both TF and PT (e.g. TF 2.8 requires python >= 3.7). As for the onnx test, let's not worry about it, since it is failing on master as well. |
I see that there are further errors in the tests, I will take a look (I think I know how to fix it). I will ping here again when the related fix is merged. Hah, it seems like you got the best model to apply |
@cakiki I've been working on issues related to TF GPT-2, and it seems like I've also solved the errors here. I've tested locally with these changes on top of We've recently renamed our branch from |
@gante Thank you for the update! |
The failing test is being tracked internally -- merging @cakiki thank you for the contribution! (and for the patience) |
What does this PR do?
Addresses #16051
Before submitting
Pull Request section?
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@gante @Rocketknight1