chore: Change unsupported operators log level to DEBUG

[peri044]

Signed-off-by: Dheeraj Peri [email protected]

Description

Change unsupported operators log level to DEBUG

Type of change

Please delete options that are not relevant and/or add your own.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project (You can use the linters)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas and hacks
• I have made corresponding changes to the documentation
• I have added tests to verify my fix or my feature
• New and existing unit tests pass locally with my changes

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[narendasan]

I think we should just use the suppress_errors message in the fallback case instead of throwing this in debug. We just need to find the right code path here

[peri044]

I think we should just use the suppress_errors message in the fallback case instead of throwing this in debug. We just need to find the right code path here

Modified it now

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[narendasan]

Do you have a script that would output the confusing error before this patch but not after?