Update SACCHARIS

[AlexSCFraser]

Update 2.0.1.dev21 to build 6, timeout adjustment and more debug logging added to solve database installation issue.

---

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

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in 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 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/<team> and will automatically re-post them to notify the addressed <team>.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves updates to the meta.yaml file for the SACCHARIS package. The version number has been incremented from 2.0.1.dev21 to 2.0.1.dev21, and the build number has changed from 5 to 6. The hash value has been updated from 551DE1D7B666A5AD693DD61F58A2617BAB3F708836D0143A7FBB981365F45AF4 to 9C58E73A2CEFE90FA2E9744E9A912CA53E383D7F587C1A2516B3E57BF14C86F9, indicating a change in the integrity check of the source package. The source URL has been modified to reflect the new build number, changing from saccharis-2.0.1.dev21_5.tar.gz to saccharis-2.0.1.dev21_6.tar.gz. The build section has been updated to include the new build number, while the preserve_egg_dir comment remains unchanged. The requirements section continues to specify necessary dependencies, and the app section retains its configuration. The test section lists commands for testing the package functionality, ensuring that the output is suppressed. Overall, the changes focus on versioning and source URL updates without altering the package's logic or functionality.

Possibly related PRs

• Update Saccharis #51314: This PR updates the meta.yaml file for the SACCHARIS package, changing the version and hash, which directly relates to the versioning and hash updates in the main PR.
• Update Saccharis #51679: This PR also updates the meta.yaml for SACCHARIS, modifying the hash and source URL, which aligns with the changes made in the main PR.
• Update SACCHARIS #51846: This PR reflects updates to the SACCHARIS package's meta.yaml, including changes to the version, hash, and source URL, which are consistent with the main PR's modifications.
• Update Saccharis #51917: This PR updates the SACCHARIS package's meta.yaml, specifically changing the hash and source URL, which directly relates to the changes in the main PR.

Suggested labels

please review & merge

Suggested reviewers

• martin-g

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

recipes/saccharis/meta.yaml (2)

17-17: Build number increment looks good, but Python version requirements need alignment.

The build number has been correctly incremented to 6. However, I noticed that the Python version requirements differ between host (>=3.6) and run (>=3.8) sections. Consider aligning these to prevent potential compatibility issues.

  host:
-   - python >=3.6
+   - python >=3.8
    - setuptools
    - pip

---

Line range hint 58-62: Consider cleaning up commented pip installation notes.

These commented instructions about PyQt5 installation issues could be moved to the repository's documentation or issues tracker for better maintainability.

-#    sort out pyqt5 install issues, sometimes pip seemed to install it with fewer errors?
-#    - pip:
-#        - lxml >=4.9.0
-#        - pyqt >=5,<6
-#        - pyqt5-sip >=12.11

🧰 Tools

🪛 yamllint

[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b0bba23 and 788a377.

📒 Files selected for processing (1)

• recipes/saccharis/meta.yaml (2 hunks)

🔇 Additional comments (2)

recipes/saccharis/meta.yaml (2)

12-12: LGTM! Source URL updated correctly.

The source URL has been properly updated to reflect the new build number while maintaining the same version.

---

3-3: LGTM! Verify the SHA256 hash.

The new SHA256 hash format is valid. However, it's good practice to verify it matches the source tarball.

[AlexSCFraser]

@BiocondaBot please add label