AssertionError: Bad argument number for Name: 3, expecting 4
See original GitHub issue–> model = MultiLabelClassifier(base_model=DistilBERT, batch_size=2, multi_label_sequences=True, n_epochs=3) –> model.fit(trainX, trainY)
WARNING: Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f4ab843b3c8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, export AUTOGRAPH_VERBOSITY=10
) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f4ab843b3c8>>: AssertionError: Bad argument number for Name: 3, expecting 4
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
Bad argument number for Name: 3, expecting 4 · Issue #1 ...
I was trying to first run this model : https://www.tensorflow.org/beta/tutorials/generative/cvae to see how it works.
Read more >tensor flow Bad argument number for Name: 3, expecting 4
When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output.
Read more >[TensorFlow] AssertionError: Bad argument number for Name
[TensorFlow] AssertionError: Bad argument number for Name: 3, expecting 4. System information Have I written custom code (as opposed to using a ...
Read more >Bad argument number for Name: 3, expecting 4 (bug)_Felaim ...
1. WARNING: Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f4ab843b3c8>> could not be transformed and ...
Read more >tensor flow Bad argument number for Name: 3, expecting 4-
tensor flow Bad argument number for Name: 3, expecting 4今天在运行t f1.14的tensorflow程序的时候出现了下面的warning,非常的多, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the reminder – 0.8.4 is now live.
Thanks for the bug report, I can reproduce the second issue. For now you can set the kwarg chunk_long_sequences=False and this should reinstate the previous behaviour.