Update dapcy to 1.0.1

[BiocondaBot]

Update dapcy: 0.1.1 → 1.0.1

Info	Link or Description
Recipe	recipes/dapcy (click to view/edit other files)
Summary	An sklearn implementation of discriminant analysis of principal components (DAPC) for population genetics.
Home	https://gitlab.com/uhasselt-bioinfo/dapcy
Releases	https://pypi.org/pypi/dapcy/json
Recipe Maintainer(s)	@pmoris

---

This pull request was automatically generated (see docs).

[coderabbitai]

Warning

Rate limit exceeded

@mencian has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 12 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 for further information.

📥 Commits

Files that changed from the base of the PR and between d3c40b1 and bd5b345.

📝 Walkthrough

📝 Walkthrough

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the dapcy package. The main changes include incrementing the version number from 0.1.1 to 0.1.2 and updating the SHA256 checksum for the source tarball from b62440ea8523f05597cd0a889b9eafb68192bd4e481048e859b772ac654ccb93 to f9c3833a74fc57c8d2c04545dc02a39d5283fb37fac9e0f93e208d614acbfa76. No additional modifications to the structure or content of the file were made. This update is part of maintaining the package and ensuring the integrity of the source code through the updated checksum.

Possibly related PRs

• Update dxpy to 0.383.1 #50990: The dxpy package update involves a version increment and SHA256 checksum change in its meta.yaml, similar to the changes made in the dapcy package's meta.yaml.
• Update pybiolib to 1.2.181 #51015: The pybiolib package update also includes a version increment and SHA256 checksum update in its meta.yaml, paralleling the changes in the dapcy package.
• Update apscale to 2.0.3 #51068: The apscale package update reflects a version change and SHA256 checksum update in its meta.yaml, akin to the modifications in the dapcy package.
• Update afpdb to 0.2.2 #51083: The afpdb package update features a version increment and SHA256 checksum change in its meta.yaml, similar to the changes in the dapcy package.
• Update savana to 1.2.2 #51103: The savana package update includes a version increment and SHA256 checksum update in its meta.yaml, paralleling the changes made in the dapcy package.
• Update sizemeup to 1.2.3 #51114: The sizemeup package update reflects a version change and SHA256 checksum update in its meta.yaml, akin to the modifications in the dapcy package.
• Update pcaone to 0.4.6 #51130: The pcaone package update involves a version increment and SHA256 checksum change in its meta.yaml, similar to the changes made in the dapcy package.
• Update pysradb to 2.2.2 #51132: The pysradb package update also includes a version increment and SHA256 checksum update in its meta.yaml, paralleling the changes in the dapcy package.
• Update bactopia-py to 1.2.0 #51154: The bactopia-py package update features a version increment and SHA256 checksum change in its meta.yaml, similar to the changes in the dapcy package.
• Update dnaio to 1.2.2 #51157: The dnaio package update reflects a version change and SHA256 checksum update in its meta.yaml, akin to the modifications in the dapcy package.

---

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.

[pmoris]

Looks good overall, but I'd like to understand why:

• the seaborn dependency was changed to seaborn-base. What is this package even? https://pypi.org/project/seaborn-base/
• The pip check and requires: pip line were removed => these were automatically generated by the initial grayskull template.
• Likewise for the build script.

EDIT: the Azure pipeline check seems to be stuck too. Any way to cancel it? Pushing a new (rebased/merged) commit might do the trick I guess?