KEMBAR78
Allow passing encoder_ouputs as tuple to EncoderDecoder Models by jsnfly · Pull Request #16814 · huggingface/transformers · GitHub
Skip to content

Conversation

@jsnfly
Copy link
Contributor

@jsnfly jsnfly commented Apr 18, 2022

What does this PR do?

Fixes #15536

For now I have added a test of the functionality to an existing test, since I'm not sure if there should be a separate test (or a test at all) for such a minor issue. Let me know if there is a better way.

Before submitting

Who can review?

@patrickvonplaten

@HuggingFaceDocBuilderDev
Copy link

HuggingFaceDocBuilderDev commented Apr 18, 2022

The documentation is not available anymore as the PR was closed or merged.

@patrickvonplaten patrickvonplaten merged commit 51e0ebe into huggingface:main Apr 18, 2022
@jsnfly jsnfly deleted the allow-passing-encoder-ouputs-as-tuple branch April 24, 2022 07:48
elusenji pushed a commit to elusenji/transformers that referenced this pull request Jun 12, 2022
…ngface#16814)

* Add passing encoder_outputs as tuple to existing test

* Add check for tuple

* Add check for tuple also for speech and vision

Co-authored-by: jsnfly <jsnfly@gmx.de>
@espoirMur
Copy link

@jsnfly , thanks you for this PR... Is it possible to do this fix for a T5 model as well.. It is also a sequence to sequence models and sometime we may want to pass a tuple to the decoder.

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 this pull request may close these issues.

Error when passing encoder_outputs as tuple to EncoderDecoder models

4 participants