-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle name conflict (attribute parameter) when converting back to python #1166
Conversation
Signed-off-by: Ganesan Ramalingam <[email protected]>
Signed-off-by: Ganesan Ramalingam <[email protected]>
Signed-off-by: Ganesan Ramalingam <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1166 +/- ##
==========================================
- Coverage 78.55% 78.52% -0.03%
==========================================
Files 118 118
Lines 15154 15231 +77
Branches 1620 1635 +15
==========================================
+ Hits 11904 11960 +56
- Misses 2872 2891 +19
- Partials 378 380 +2 ☔ View full report in Codecov by Sentry. |
Test Results 18 files ±0 18 suites ±0 1h 9m 40s ⏱️ + 11m 35s For more details on these failures, see this check. Results for commit 632d44b. ± Comparison against base commit 10f9a1f. This pull request skips 1 test.
♻️ This comment has been updated with latest results. |
Attribute parameters and normal values (like tensors) use the same namespace in onnxscript/python. This can cause a conflict when converting ONNX proto back to onnxscript (since these are different namespaces in ONNX). Examples of where this happens shown in test-case below: eg., when an attribute-parameter "yyy" is used as a value, the onnxscript translator introduces a value called "yyy" which is bound to the attribute-value "yyy".
Fix this in the exporter.