ci(fuzz): Run read_zipfile_from_stream at end of test case when possible

[Pr0methean]

No description provided.

[amazon-q-developer]

⏳ Code review in progress. Analyzing for code quality issues and best practices. Detailed findings will be posted upon completion.

Using Amazon Q Developer for GitHub

Amazon Q Developer¹ is an AI-powered assistant that integrates directly into your GitHub workflow, enhancing your development process with intelligent features for code development, review, and transformation.

Slash Commands

Command	Description
/q <message>	Chat with the agent to ask questions or request revisions
/q review	Requests an Amazon Q powered code review
/q help	Displays usage information

Features

Agentic Chat
Enables interactive conversation with Amazon Q to ask questions about the pull request or request specific revisions. Use /q <message> in comment threads or the review body to engage with the agent directly.

Code Review
Analyzes pull requests for code quality, potential issues, and security concerns. Provides feedback and suggested fixes. Automatically triggered on new or reopened PRs (can be disabled for AWS registered installations), or manually with /q review slash command in a comment.

Customization

You can create project-specific rules for Amazon Q Developer to follow:

1. Create a .amazonq/rules folder in your project root.
2. Add Markdown files in this folder to define rules (e.g., cdk-rules.md).
3. Write detailed prompts in these files, such as coding standards or best practices.
4. Amazon Q Developer will automatically use these rules when generating code or providing assistance.

Example rule:

All Amazon S3 buckets must have encryption enabled, enforce SSL, and block public access.
All Amazon DynamoDB Streams tables must have encryption enabled.
All Amazon SNS topics must have encryption enabled and enforce SSL.
All Amazon SNS queues must enforce SSL.

Feedback

To provide feedback on Amazon Q Developer, create an issue in the Amazon Q Developer public repository.

For more detailed information, visit the Amazon Q for GitHub documentation.

Footnotes

1. Amazon Q Developer uses generative AI. You may need to verify generated code before using it in your environment. See the AWS Responsible AI Policy. ↩

[gemini-code-assist]

Summary of Changes

Hello @Pr0methean, 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 fuzzing suite for the zip crate by introducing a new test path. It enables the fuzzer to attempt reading generated ZIP files via a stream-based API (read_zipfile_from_stream) when the file's characteristics allow for it, thereby improving the robustness and coverage of the fuzz tests against potential stream-related vulnerabilities or edge cases.

Highlights

• Enhanced Fuzzing for Stream Reading: Introduced a new is_streamable check within the fuzzing framework to determine if a generated ZIP file can be read via a stream.
• Conditional Stream Reading in Fuzz Tests: Modified the fuzz test execution to, when possible, read the generated ZIP file using read_zipfile_from_stream instead of finish_into_readable. This expands fuzzing coverage for stream-based ZIP parsing.

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

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

[amazon-q-developer]

I've reviewed the changes to the fuzzing infrastructure that add streaming functionality testing. The implementation looks solid overall, with a few suggestions for improvement:

1. The new is_streamable method is a good addition but could be more readable with some restructuring
2. The stream reading logic could benefit from being extracted into a separate function
3. Some additional documentation would help future maintainers understand the purpose of certain variables

The changes appear to enhance the test coverage by validating the streaming functionality, which is valuable for ensuring reliability. The approach of checking streamability before attempting stream operations is well thought out.

[gemini-code-assist]

Code Review

This pull request enhances the fuzz testing capabilities by incorporating tests for read_zipfile_from_stream. A new is_streamable method is introduced to identify which zip operations can be tested with the streaming reader, and the fuzz test execution logic is updated accordingly. The overall approach is sound, but I've identified a critical syntax error that would prevent the fuzzer's debug output from compiling, as well as an opportunity to simplify the new is_streamable method.