Skip to content

Only emit one error for each unsupported operator encountered #650

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

Merged
merged 2 commits into from
Apr 2, 2025

Conversation

robertknight
Copy link
Owner

During model conversion, if an unsupported operator is used by many nodes, only emit one message per operator type. This makes the output less noisy.

  • Add ConversionError base class for all exceptions during conversion

  • Add UnsupportedOperatorError subclass for unsupported operator
    exceptions and use this to keep a memory of the unique operators for
    which a warning has been emitted.

Give this utility a name which matches its functionality better.
If an unsupported operator is used by many nodes, only emit one message
per operator. This makes the output less noisy.

 - Add `ConversionError` base class for all exceptions during conversion

 - Add `UnsupportedOperatorError` subclass for unsupported operator
   exceptions and use this to keep a memory of the unique operators for
   which a warning has been emitted.
@robertknight robertknight merged commit 0101455 into main Apr 2, 2025
2 checks passed
@robertknight robertknight deleted the unsupported-op-warn-once branch April 2, 2025 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant