Mitigate Missing cell-eval watermark warnings caused by oversized VCC files.

[bingooo]

Mitigate watermark warnings caused by oversized VCC files.

Invalid file: Missing cell-eval watermark. Please run file through the cell-eval prep tool.

[gemini-code-assist]

Summary of Changes

Hello @bingooo, 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 addresses and mitigates watermark warnings that were occurring due to oversized VCC files. The solution involves a minor but critical adjustment to the sequence of file arguments passed to a processing command, ensuring that all necessary components are handled in the correct order to prevent these warnings.

Highlights

• File Processing Order: The order of pred.h5ad.zst and watermark.txt arguments within a subprocess.run command in the strip_anndata function has been reordered. This change ensures correct processing of these files, which is crucial for mitigating watermark warnings caused by oversized VCC files.

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 correctly reorders the files within the generated tar archive to place watermark.txt first. This change should resolve the watermark warnings from oversized VCC files as intended. I have added one high-severity suggestion to improve error handling by adding check=True to the subprocess.run call, which will prevent silent failures if the tar command encounters an error.