Skip to content

chore: work around setuptools 76 hash mismatch from March 9, 2025 #3370

Merged
johanneskoester merged 3 commits intomainfrom
chore/setuptools-workaround
Mar 11, 2025
Merged

chore: work around setuptools 76 hash mismatch from March 9, 2025 #3370
johanneskoester merged 3 commits intomainfrom
chore/setuptools-workaround

Conversation

@johanneskoester
Copy link
Copy Markdown
Contributor

@johanneskoester johanneskoester commented Mar 11, 2025

Description

QC

  • The PR contains a test case for the changes or the changes are already covered by an existing test case.
  • The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Summary by CodeRabbit

  • Chores
    • Streamlined dependency management to consolidate package installations for a more consistent and reliable setup process.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 11, 2025

📝 Walkthrough

Walkthrough

The test-environment.yml file has been updated to change how dependencies are managed. Specifically, the dependencies for cwltool and cwl-utils have been moved from the pip section to the main dependencies list, meaning they will now be installed via conda instead of pip.

Changes

File Change Summary
test-environment.yml Removed cwltool and cwl-utils from the pip section and added them to the main dependencies list.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d1c369b and 663ccb9.

⛔ Files ignored due to path filters (1)
  • pyproject.toml is excluded by !pyproject.toml
📒 Files selected for processing (2)
  • test-environment.yml (1 hunks)
  • test-environment.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (40)
  • GitHub Check: testing (10, 3.12, dash)
  • GitHub Check: testing (10, 3.12, bash)
  • GitHub Check: testing (10, 3.11, bash)
  • GitHub Check: testing (9, 3.12, dash)
  • GitHub Check: testing (9, 3.12, bash)
  • GitHub Check: testing (9, 3.11, bash)
  • GitHub Check: testing (8, 3.12, dash)
  • GitHub Check: testing (8, 3.12, bash)
  • GitHub Check: testing (8, 3.11, bash)
  • GitHub Check: testing (7, 3.12, dash)
  • GitHub Check: testing (7, 3.12, bash)
  • GitHub Check: testing (7, 3.11, bash)
  • GitHub Check: testing (6, 3.12, dash)
  • GitHub Check: testing (6, 3.12, bash)
  • GitHub Check: testing (6, 3.11, bash)
  • GitHub Check: testing (5, 3.12, dash)
  • GitHub Check: testing (5, 3.12, bash)
  • GitHub Check: testing (5, 3.11, bash)
  • GitHub Check: testing (4, 3.12, dash)
  • GitHub Check: testing (4, 3.12, bash)
  • GitHub Check: testing-windows (10)
  • GitHub Check: testing (4, 3.11, bash)
  • GitHub Check: testing-windows (9)
  • GitHub Check: testing (3, 3.12, dash)
  • GitHub Check: testing-windows (8)
  • GitHub Check: testing (3, 3.12, bash)
  • GitHub Check: testing-windows (7)
  • GitHub Check: testing (3, 3.11, bash)
  • GitHub Check: testing (2, 3.12, dash)
  • GitHub Check: testing-windows (6)
  • GitHub Check: testing (2, 3.12, bash)
  • GitHub Check: testing-windows (5)
  • GitHub Check: testing (2, 3.11, bash)
  • GitHub Check: testing (1, 3.12, dash)
  • GitHub Check: testing-windows (4)
  • GitHub Check: testing (1, 3.12, bash)
  • GitHub Check: testing-windows (3)
  • GitHub Check: testing (1, 3.11, bash)
  • GitHub Check: testing-windows (2)
  • GitHub Check: testing-windows (1)
🔇 Additional comments (1)
test-environment.yml (1)

61-62:

Details

❓ Verification inconclusive

Dependency Update: Installing cwltool and cwl-utils via Conda

Moving these two dependencies from the pip section to the main dependencies list ensures that they are now installed via conda. This change should help work around the setuptools 76 hash mismatch issues that can occur with pip. Please verify that both packages are available and up-to-date in your specified conda channels (e.g., conda-forge or bioconda), so that the installation remains stable and consistent.


Based on the snippet in test-environment.yml (lines 61–62) showing the dependencies:

  - cwltool
  - cwl-utils

the changes correctly reflect that these dependencies are now listed in the main dependencies (thus to be installed via conda) as opposed to being in the pip section. This update is intended to work around setuptools 76 hash mismatch issues associated with pip.

Please verify on your side that:

  • Both cwltool and cwl-utils are available in the intended conda channels (e.g., conda-forge or bioconda).
  • The packages are up-to-date in these channels to ensure stable installation.

Dependency Update Verified: Confirm Conda Package Availability

  • Verify lines 61–62 in test-environment.yml reflect the changes.
  • Confirm cwltool and cwl-utils are current in your conda channels.

🏁 Script executed:

#!/bin/bash
# Display lines 60 to 70 of test-environment.yml to verify that the cwltool and cwl-utils changes are in place
sed -n '60,70p' test-environment.yml

Length of output: 318


Dependency Update Verified:
The output from test-environment.yml confirms that the dependencies are now correctly listed under the conda dependencies section:

  • - cwltool
  • - cwl-utils

Please ensure that these packages are also available and kept up-to-date in your preferred conda channels (e.g., conda-forge or bioconda) to maintain a stable installation and work around the setuptools 76 hash mismatch issues.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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 generate docstrings to generate docstrings for this 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.

@johanneskoester johanneskoester changed the title Chore/setuptools-workaround chore: work around setuptools 76 hash mismatch from March 9, 2025 Mar 11, 2025
@sonarqubecloud
Copy link
Copy Markdown

@johanneskoester johanneskoester merged commit 477e5f8 into main Mar 11, 2025
50 checks passed
@johanneskoester johanneskoester deleted the chore/setuptools-workaround branch March 11, 2025 10:19
kjohnsen pushed a commit to kjohnsen/snakemake that referenced this pull request Dec 15, 2025
…akemake#3370)

### Description

<!--Add a description of your PR here-->

### QC
<!-- Make sure that you can tick the boxes below. -->

* [x] The PR contains a test case for the changes or the changes are
already covered by an existing test case.
* [x] The documentation (`docs/`) is updated to reflect the changes or
this is not necessary (e.g. if the change does neither modify the
language nor the behavior or functionalities of Snakemake).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Streamlined dependency management to consolidate package installations
for a more consistent and reliable setup process.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant