-
Notifications
You must be signed in to change notification settings - Fork 1
feat: add download_spec_tests executable #45
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
Conversation
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 @wemeetagain, 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 introduces a new executable that automates the process of downloading and extracting Ethereum consensus spec tests. This enhancement streamlines the setup for testing environments by providing a dedicated tool to fetch necessary test data, configurable through build options.
Highlights
- New Executable: A download_spec_tests executable has been added to facilitate the automated download and extraction of Ethereum consensus spec tests.
- Configurable Options: The executable's behavior, including the spec test URL, version, and output directory, can be customized via an options module, allowing overrides through zbuild.zon or command-line flags.
- Build System Integration: The new executable is fully integrated into the build system, allowing it to be run using zbuild run download_spec_tests or zig build run:download_spec_tests.
- Test Data Management: The .gitignore file has been updated to properly ignore the downloaded spec test directory, ensuring clean repository state.
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. 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. ↩
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 introduces a new executable script for downloading consensus spec tests, which is a great addition for managing test data. The changes to the build configuration in build.zig
and zbuild.zon
are well-structured. However, the implementation of the download script in test/spec/download_spec_tests.zig
contains a critical bug in the file download logic, a resource leak, and some areas where error handling could be improved. I've provided specific comments and code suggestions to address these points.
Performance Report✔️ no performance regression detected Full benchmark results
|
* feat: add download_spec_tests executable * chore: resource cleanup * chore: resource cleanup
zbuild run download_spec_tests
orzig build run:download_spec_tests
to execute