Update get_all_grader_info logic.

[weizhang25]

Update get_all_grader_info logic according to the AI suggestions in the previous PR.

[gemini-code-assist]

Summary of Changes

Hello @weizhang25, 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 grader_info utility by streamlining how grader files are discovered and how method signatures within those files are parsed. The changes introduce a more efficient and readable approach for recursive file system navigation and significantly improve the accuracy of extracting function definitions from source code, contributing to better maintainability and reliability of the grader information system.

Highlights

• File Traversal Refactor: The logic for recursively finding Python files in the graders directory has been simplified by replacing a manual Queue-based traversal with the more concise and Pythonic Path.rglob method.
• Improved Function Signature Parsing: The _parse_grader_class_def function now uses a more robust algorithm to extract method signatures. It tracks parenthesis depth to accurately identify the end of a function definition, handling complex type hints more reliably than the previous string-based search.
• Dependency Cleanup: The unused Queue import has been removed from openjudge/utils/grader_info.py as it is no longer required by the updated file traversal logic.

🧠 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.

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 refactors the logic in get_all_grader_info. The changes include simplifying file discovery by using pathlib.Path.rglob instead of manual directory traversal, and updating the function signature parsing logic. The file discovery change is a good simplification. However, the new signature parsing logic, while an improvement over the previous string-based search, is still susceptible to errors when colons appear in string literals or default values within function arguments. I've provided a more robust solution that leverages the AST structure to reconstruct the signature, which should handle these edge cases correctly.