Fix innocuous tracer warnings in onnx export#42
Merged
dlangerm-stackav merged 1 commit intoJun 17, 2026
Conversation
dlangerm
force-pushed
the
dlangerm/fix-trace-warnings
branch
3 times, most recently
from
3c933bc to
ecc87f8
Compare
dlangerm
force-pushed
the
dlangerm/fix-trace-warnings
branch
from
ecc87f8 to
78a1828
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Ignores tracer warnings during onnx export, these warnings are innocuous as dltype doesn't alter the compute graph in any way, we merely inspect shapes and datatypes.
Testing
Please select all that apply.
Test instructions