-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Control flow issue with symbolic_trace when using inputs_embeds in MistralForCausalLM #31200
Comments
cc @fxmarty and @michaelbenayoun |
1 similar comment
cc @fxmarty and @michaelbenayoun |
can u help me ? @fxmarty and @michaelbenayoun |
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Hi @Hongjie1Chu, this should be fixed on the main branch with #31574. |
System Info
transformers
version: 4.41.2Who can help?
@ArthurZucker @younesbelkada @Narsil
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
when i use dummy_input_ids to trace ,no error,but when i use dummy_inputs_embeds to trace ,error:
Expected behavior
I would like to know why using input_ids allows for normal tracing, and there are no errors when executing if seq_len > self.max_seq_len_cached;, but switching to inputs_embeds causes an issue at this point?
"If I must trace using
inputs_embeds
, how should I proceed? I am working on a pipeline job and need to construct parts of the model as follows:model1:
model2:
So, model2 can only be traced using
inputs_embeds
. How should I modify it?"The text was updated successfully, but these errors were encountered: