You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
When this op is use in a nested gluon block, it's a bit hard to investigate what are the actual types of input 0 and input 1. It will be much more helpful if the actual data types can be printed.
The text was updated successfully, but these errors were encountered:
@eric-haibin-lin ,
Got similar issue when trying to use the np.dstack api. I submit above PR for this. Please kindly help to review if you could. Thanks.
* Fix#17267, add expected and got datatype when non-uniform dtype fount in concat
* Add op name and input index to concat type error msg
* Fix lint error
litaotju
added a commit
to litaotju/incubator-mxnet
that referenced
this issue
Jan 17, 2020
Description
mxnet.np.dstack
throws dtype mismatch if one input isint32
and the other isfloat32
. However, the error message is not that clear:When this op is use in a nested gluon block, it's a bit hard to investigate what are the actual types of input 0 and input 1. It will be much more helpful if the actual data types can be printed.
The text was updated successfully, but these errors were encountered: