[Misc] Better debugging and guards to autowrapping

[kylesayrs]

Purpose

• Improve debugging for autowrapper

Changes

• Check that model implements forward method. Models which do not implement a forward method cannot be calibrated, neither with the sequential pipe nor the basic pipeline
• Append autowrapped code during interpreter compilation of autowrapped code
  • Makes debugging issues with interpreter recompilation easier
• Change append_autowrap_source_on_fail to append autowrap source code before actual failure reason

[github-actions]

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

[gemini-code-assist]

Summary of Changes

Hello @kylesayrs, 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 primarily focuses on bolstering the robustness and debuggability of the autowrapping functionality. It introduces a crucial guard to prevent errors when processing models that lack a defined forward method and refines the error reporting mechanism to provide more immediate and useful context for debugging autowrapped code. Additionally, it includes a minor refinement to type hints for improved code clarity.

Highlights

• Improved Autowrapping Guards: A new check has been added to the autowrap_forward function to ensure that models implement a forward method, preventing calibration issues for models that do not define one.
• Enhanced Debugging for Autowrapped Code: The autowrapped code is now appended during interpreter compilation, and the append_autowrap_source_on_fail context manager has been modified to display the autowrapped source code before the actual failure reason in error messages, significantly improving debugging clarity.
• Type Hint Simplification: The type hints for the data_collator_with_truncation function have been shortened for better readability and conciseness.

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

1. 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. ↩

[gemini-code-assist]

Code Review

This pull request improves debugging for the autowrapper and adds a guard to check for forward method implementation. The changes are generally good, but I've found a critical issue with exception handling that will cause a TypeError. I've also suggested reverting a change to type hints to maintain code clarity and type safety.