This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Floating point exception in mxnet.ndarray.op.SequenceReverse #18940
Labels
Comments
So here's the problem:
The code needs to guard against zero-size array for right operand of |
szha
added
good first issue for c++ developer
v1.x
Targeting v1.x branch
C++
Related to C++
good first issue
and removed
good first issue for c++ developer
labels
Aug 21, 2020
r3stl355
pushed a commit
to r3stl355/incubator-mxnet
that referenced
this issue
Feb 7, 2021
r3stl355
pushed a commit
to r3stl355/incubator-mxnet
that referenced
this issue
Feb 9, 2021
Could I get this assigned?? |
Hello, |
It seems like there is an arithmetic error in the code where the right operand of the division operator is zero, causing an EXC_ARITHMETIC exception. One way to guard against this error is to add a conditional statement that checks if the right operand is zero before executing the division operation. can i work on it if it's still open? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
(A clear and concise description of what the bug is.)
mxnet.ndarray.op.SequenceReverse
has floating point exception when givendata
has 0 in its shape. Please see the provided code for example.Error Message
(Paste the complete error message. Please also include stack trace by setting environment variable
DMLC_LOG_STACK_TRACE_DEPTH=10
before running your script.)To Reproduce
(If you developed your own code, please provide a short script that reproduces the error. For existing examples, please provide link.)
Steps to reproduce
(Paste the commands you ran that produced the error.)
What have you tried to solve it?
Environment
We recommend using our script for collecting the diagnositc information. Run the following command and paste the outputs below:
Got 404 when trying to get the script.
Some environment information:
The text was updated successfully, but these errors were encountered: