coderabbitai[bot]
commented
6 days ago [!WARNING]
Rate limit exceeded
@mencian has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 23 seconds before requesting another review.
⌛ How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.🚦 How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.📥 Commits
Files that changed from the base of the PR and between 2b2e041aa75dc6a48723d7129b09dcb8486f9bf8 and 154dfd86648d39554d909c4ffc71a85a13f79457.
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
## Walkthrough A new metadata file for the `mutyper` package has been introduced, detailing its configuration for package management. The file specifies the package name as "mutyper" and its version as "1.0.2". The source section provides a URL for downloading the package from PyPI, along with a SHA256 checksum for integrity verification. The build section outlines the build process, including run exports for the `mutyper` subpackage, a build number, and environment variables for the build script. The script for installation utilizes pip with specific flags to avoid dependency isolation and caching. The entry point for the package is defined as `mutyper.cli:main`. Requirements are categorized into build, host, and run sections. The build requirements include the C compiler and make. The host requirements specify Python, pip, and setuptools. The run requirements include Python, pandas, cyvcf2, pyfaidx, biopython, and pyliftover, with a specific version constraint for cyvcf2. The test section includes commands to verify the installation by importing the `mutyper` package and executing various help commands for its subcommands. The about section provides metadata about the package, including its homepage, license information, a summary of its functionality, and a documentation URL. ## Possibly related PRs - **#51139**: The `mutamr` package introduces a new metadata file similar to the `mutyper` package, detailing its configuration for building and installation, including a `run_exports` section. - **#51140**: This PR also involves the `mutamr` package and includes a new metadata file, which shares structural similarities with the `mutyper` package's metadata file. - **#51178**: The `get_mnv` package introduces a new metadata file that outlines its configuration, akin to the `mutyper` package's metadata structure. - **#51326**: The `seqspec` package's metadata file is structured similarly to the `mutyper` package, detailing its configuration for building and installation. - **#51355**: The `longcallr_nn` package introduces a new metadata file that outlines its configuration, similar to the `mutyper` package's metadata structure. ## Suggested labels `please review & merge`Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Add mutyper to bioconda.
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add labelcommand.@bioconda/corein a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes. This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe. If not already present in the meta.yaml, make sure to specify
run_exports(see here for the rationale and comprehensive explanation). Add arun_exportssection like this:with
...being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}while replacing
"myrecipe"with eithernameif aname|lowervariable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:@BiocondaBot please update@BiocondaBot please add labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
@BiocondaBot please mergecommand is now depreciated. Please just squash and merge instead. Also, the bot watches for comments from non-members that include `@bioconda/