-
Notifications
You must be signed in to change notification settings - Fork 184
[Autowrapper] Fix local names, increase reproducability #1672
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Kyle Sayers <kylesayrs@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @kylesayrs, I'm Gemini Code Assist1! 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 significantly improves the Autowrapper
utility by addressing a critical bug that prevented proper recognition of args
and kwargs
as local names, which was necessary for certain model architectures. Beyond the bug fix, the changes also focus on making the autowrapper's behavior more deterministic and easier to debug by standardizing the naming of wrapped functions and the ordering of their arguments. The accompanying test suite has been updated and expanded to reflect these improvements and ensure robust functionality.
Highlights
- Bug Fix: Local Name Recognition: Resolved a critical bug where
args
andkwargs
were not correctly recognized as local names within the autowrapper's scope, specifically impacting models like Kimi K2 that utilize such constructs. - Improved Debuggability and Reproducibility: Enhanced the autowrapper's output consistency by switching from hash-based naming to an incrementing counter for wrapped functions and ensuring consistent sorting of arguments and return values in the generated code. This makes debugging and tracing much more predictable.
- Test Suite Refinement: Refactored existing autowrapper tests for improved clarity and maintainability. A new test case,
test_function_variadic
, was added to specifically validate the autowrapper's handling of functions with variadic arguments (*args
and**kwargs
).
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 or fill out our survey to provide feedback.
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. ↩
👋 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request fixes an important bug related to recognizing all argument types in function definitions for autowrapping, which improves model compatibility. The change to use a counter for wrapped function names is a good step towards reproducibility. The test suite has been significantly refactored for clarity and robustness.
I've found a couple of minor issues:
- The code for collecting function arguments can be made more concise.
- The test refactoring revealed a bug in the code generation logic where wrapped functions can contain unreachable
return
statements.
I've left comments with suggestions for these points. Overall, this is a solid contribution.
tests/llmcompressor/pipelines/sequential/ast_utils.py/test_auto_wrapper.py
Show resolved
Hide resolved
tests/llmcompressor/pipelines/sequential/ast_utils.py/test_auto_wrapper.py
Show resolved
Hide resolved
Signed-off-by: Kyle Sayers <kylesayrs@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very impressive
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Purpose
args
andkwargs
were not being recognized as local names in the namespace when autowrappingChanges
Testing
test_function_variadic