search

bioconda / bioconda-recipes

Conda recipes for the bioconda channel.
https://bioconda.github.io
MIT License
1.64k stars 3.27k forks source link

bump sainsc build number #51768

Closed aliciaaevans closed 2 days ago

aliciaaevans commented 2 days ago

Due to CI transitions, sainsc didn't get properly uploaded.

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

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 a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case run_exports statement
semantic versioning {{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x) {{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions {{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions {{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning {{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable 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 Merge the master branch into a PR.
@BiocondaBot please add label Add the please review & merge label.
@BiocondaBot please fetch artifacts Post links to CI-built packages/containers.
You can use this to test packages locally.
Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead. Also, the bot watches for comments from non-members that include `@bioconda/` and will automatically re-post them to notify the addressed ``.
aliciaaevans commented 2 days ago

@BiocondaBot please fetch artifacts

BiocondaBot commented 2 days ago

Package(s) built are ready for inspection:

Arch Package Zip File / Repodata CI Instructions
linux-64 sainsc-0.2.1-py310hec43fc7_1.tar.bz2 linux-64.zip GitHub Actions
showYou may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>
linux-64 sainsc-0.2.1-py311h5e00ca1_1.tar.bz2 linux-64.zip GitHub Actions
showYou may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>
linux-64 sainsc-0.2.1-py312h004ce86_1.tar.bz2 linux-64.zip GitHub Actions
showYou may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>
osx-arm64 sainsc-0.2.1-py310h6e53005_1.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/44fdc2b1-44e0-405a-9fa3-c400583fd376/artifacts/0/tmp/artifacts/packages <package name>
osx-arm64 sainsc-0.2.1-py311h6d69d58_1.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/44fdc2b1-44e0-405a-9fa3-c400583fd376/artifacts/0/tmp/artifacts/packages <package name>
osx-arm64 sainsc-0.2.1-py312h717d5ad_1.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/44fdc2b1-44e0-405a-9fa3-c400583fd376/artifacts/0/tmp/artifacts/packages <package name>
linux-aarch64 sainsc-0.2.1-py310h2f7f10f_1.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/021516a2-ce1f-4335-a890-a2bdf5b06e98/artifacts/0/tmp/artifacts/packages <package name>
linux-aarch64 sainsc-0.2.1-py311h8af31a9_1.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/021516a2-ce1f-4335-a890-a2bdf5b06e98/artifacts/0/tmp/artifacts/packages <package name>
linux-aarch64 sainsc-0.2.1-py312h981cfc2_1.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/021516a2-ce1f-4335-a890-a2bdf5b06e98/artifacts/0/tmp/artifacts/packages <package name>
aliciaaevans commented 2 days ago

@coderabbitai ignore

aliciaaevans commented 2 days ago

Not sure why CodeRabbit is stuck on this one

coderabbitai[bot] commented 2 days ago
📝 Walkthrough ## Walkthrough The pull request involves modifications to the `meta.yaml` file for the `sainsc` package. The primary change is the increment of the `build.number` from `0` to `1`, indicating a new build iteration. The `skip` condition remains unchanged, still set to `True`, implying that the build will be skipped under specific conditions related to the operating system and Python version. No changes were made to the package dependencies, requirements, or other sections of the file, ensuring that the existing structure and content are preserved. ## Possibly related PRs - #51203: The `meta.yaml` file for the `r-cobrar` package has a similar change where the build number is incremented from `0` to `1`, directly relating to the change made in the main PR. - #51750: The `meta.yaml` file for the `ucsc-bedgraphtobigwig` package also reflects an increment in the build number from `0` to `1`, which is the same type of modification as in the main PR. - #51769: The `meta.yaml` file for the `prodigal-gv` package shows an increment in the build number from `3` to `4`, indicating a new build iteration, similar to the change in the main PR. ## Suggested reviewers - bgruening - daler
📜 Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
📥 Commits Files that changed from the base of the PR and between 3dab52f5f6531b98ebb45f8ab14487e64e7f6b38 and aa6f69150b0dd0ead2d19b057054ea6d79715209.
📒 Files selected for processing (1) * recipes/sainsc/meta.yaml (1 hunks)
🔇 Additional comments (1)
recipes/sainsc/meta.yaml (1) `14-14`: **LGTM! Build number increment looks correct.** The build number increment from 0 to 1 is appropriate for addressing the package upload issues without changing the package version. Let's verify there are no parallel PRs also incrementing this build number:
✅ Verification successful **Build number increment is safe to proceed** No other open PRs are modifying the sainsc recipe, confirming this is the only build number change in progress.
🏁 Scripts executed The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Description: Check for other open PRs modifying the sainsc recipe # Expected: No other PRs should be modifying the build number gh pr list --search "path:recipes/sainsc/meta.yaml is:open" --json number,title,body ``` Length of output: 89

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?

❤️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
coderabbitai[bot] commented 2 days ago

@coderabbitai ignore

:white_check_mark: Actions performed Reviews paused.
aliciaaevans commented 2 days ago

@coderabbitai resume