-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Improve error messages on shape inference (Operator) #12565
Comments
More generally, I also suggest to review the use of require() scattered in the code, and make sure they all have meaningful messages. |
Thanks for submitting the issue @mdespriee, you can open a PR with the changes you have suggested and we can review them. |
I agree. I've run into that one from the Clojure side as well and it could be improved. |
After PR #12570 is merged, we'll go from this:
to this:
I think we can have even better from the backend, but that's progress. |
@mdespriee thanks for your contribution. Looks like the PR has been merged. Can this issue be closed? |
Can it be improved from the backend side ?
If not, yes, we can close it for now.
Le jeu. 20 sept. 2018 à 18:55, Kalyanee Chendke <[email protected]>
a écrit :
… @mdespriee <https://github.com/mdespriee> thanks for your contribution.
Looks like the PR has been merged. Can this issue be closed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12565 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhFNKP5YtuRb5X8sC41yCu-XfsUPMwUks5uc8hxgaJpZM4WpjFM>
.
|
@apeforest @anirudh2290 Do you have any plan for this? |
The improvement would need to happen per operator. Let's create issues for individual operators when we discover more of these unclear messages. |
Description
I'm trying to migrate to mxnet symbol a fairly complex flow, and I spent way too much time debugging "shape inference failed" errors when binding the module.
What shape ? What symbol ? Which shape is ok, and which is missing ? Argh !
Environment info (Required)
Using mxnet 1.3.0 on scala
Error Message:
The text was updated successfully, but these errors were encountered: