Skip to content

fix: Report unsupported TFLite operators - #1309

Open
yuefdev wants to merge 1 commit into
ARM-software:mainfrom
yuefdev:fix/tflite-unsupported-operators
Open

yuefdev wants to merge 1 commit into
ARM-software:mainfrom
yuefdev:fix/tflite-unsupported-operators

Conversation

@yuefdev

@yuefdev yuefdev commented Sep 13, 2026

Copy link
Copy Markdown

The TFLite model reporter crashes on unmapped operators such as CUSTOM, IF, and WHILE because the exception message mixes {} placeholders with % formatting. Format the message correctly so the existing ValueError handler can report unsupported operators and continue generating the supported-operator configuration.

Also classify ONE_HOT as unsupported instead of writing the literal Unsupported into the supported operators list and generated JSON.

Validation: python -m unittest discover -s python/tests -v passes all 5 tests with the pinned python/requirements.txt dependencies on Python 3.10.21 / Windows x64. The tests fail on the original implementation and cover helper mappings plus subprocess CLI reporting using serialized TFLite metadata fixtures. No Arm inference or full C++ library build was run. Focused formatting, whitespace and license checks pass; the full pre-commit run encountered existing Windows tooling failures, addressed separately.

Signed-off-by: Yusuf Efe <120668197+yuefdev@users.noreply.github.com>
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