Squeeze node fails when axes is ""

[justinchuby]

Error [ONNXRuntimeError] : 6 : RUNTIME_EXCEPTION : Non-zero status code returned while running Squeeze node. Name:'node_Squeeze_141' Status Message: /onnxruntime_src/onnxruntime/core/providers/cuda/tensor/squeeze.cc:50 virtual onnxruntime::common::Status onnxruntime::cuda::Squeeze::ComputeInternal(onnxruntime::OpKernelContext*) const axes_tensor != nullptr was false. Axes input is null_ is raise when Squeeze node has a single input. According to the spec https://onnx.ai/onnx/operators/onnx__Squeeze.html, If axes is not provided, all the single dimensions will be removed from the shape. If an axis is selected with shape entry not equal to one, an error is raised.

cc @xadupre @gramalingam

[github-actions]

This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details.

[justinchuby]

cc @shubhambhokare1 this is a similar issue

[titaiwangms]

Who would be the right contact for this op? @gramalingam

[gramalingam]

Hi, I updated the title and label based on my recollection. I believe that this is a corner case where onnxruntime does not fully support the onnx spec concerning optional trailing inputs. The ONNX spec says that for an optional trailing input like axes (for the Squeeze op): the input can be omitted completely (number of inputs will be 1 in the node), or an empty string can be used to indicate a missing input (the node will have 2 inputs, where the second input is the empty string). The latter format is necessary when we have non-trailing optional inputs, but is allowed even for trailing optional inputs.

I think onnxruntime doesn't handle the second kind of input correctly. But, for now, the converter will avoid generating trailing inputs that are an empty string. So, it is not critical. But it would be helpful if onnxruntime fixes it (in case of models coming from other sources).