-
Notifications
You must be signed in to change notification settings - Fork 27.5k
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
Encoder-Decoder: OTP as a decoder #23350
Comments
Hey @BramVanroy 👋 I believe most, if not all, recent decoder-only models are not compatible with |
Thanks for the reply @gante! I indeed had found this difference in the code. Do you know whether there are any plans to make more decoders compatible? |
@BramVanroy not on our end, since Decoder-only models have been stealing the spotlight! We'd be happy to merge the appropriate changes, though |
Okay, that makes sense. Different priorities! Thanks for the reply João. |
Managed to find this issue after https://twitter.com/alvations/status/1763206884205425054 And then trying to do this:
Not sure if it's "useful" eventually. But it'll be nice if the above is possible. |
@gante Could you update which block you're referring to? Ideally using a permanent link if possible. Thanks! |
(@michaelmior updated with a permalink) |
can anyone suggest any decoder only model which is compatible with the graphcodeBERT? |
System Info
transformers
version: 4.29.1Who can help?
@ArthurZucker and @younesbelkada, and maybe also @gante for generation in enc/dec scenarios
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
This leads to
Expected behavior
I am trying to use the encoder-decoder functionality but I am not sure whether I am doing something wrong, or whether OPT is simply not compatible with this architecture.
The text was updated successfully, but these errors were encountered: