[Relax][ONNX] Fix get_converter edge case for unsupported low opset by lonelyeagle · Pull Request #18888

[Relax][ONNX] Fix get_converter edge case for unsupported low opset by lonelyeagle · Pull Request #18888 · apache/tvm

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the stability of the ONNX frontend by addressing a specific edge case in opset version handling. It introduces a mechanism to gracefully manage requests for ONNX opset versions that are below the minimum supported implementation, thereby preventing potential runtime errors or misinterpretations of available converters.

Highlights

Robustness for ONNX opset conversion: Implemented a guard in OnnxOpConverter.get_converter to prevent incorrect converter selection when an unsupported low opset version is requested. This ensures that attempts to use opsets lower than the minimum supported version now explicitly raise a NotImplementedError instead of potentially failing silently or selecting an invalid converter.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

python/tvm/relax/frontend/onnx/onnx_frontend.py
- Introduced opset_idx variable to store the index of the requested opset.
- Added a conditional check to raise NotImplementedError if opset_idx is 0, indicating an unsupported low opset.
- Adjusted the version calculation to use opset_idx - 1 after the new guard.

Activity

No activity has occurred on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩