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 Aug 30, 2018. It is now read-only.
Right now, if you feed onnx-caffe2 something that happens to be a valid Caffe2 operator, but not an ONNX operator, onnx-caffe2 will silently accept it. That's bad! We do not want to reward bad behavior. And with the versioning update onnx/onnx#186 we can backdoor Caffe2 ops using a vendor extension, if you absolutely need to. So... tighten this up!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, if you feed onnx-caffe2 something that happens to be a valid Caffe2 operator, but not an ONNX operator, onnx-caffe2 will silently accept it. That's bad! We do not want to reward bad behavior. And with the versioning update onnx/onnx#186 we can backdoor Caffe2 ops using a vendor extension, if you absolutely need to. So... tighten this up!
The text was updated successfully, but these errors were encountered: