Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Update dependencies to latest versions - less complex #1011

Merged
merged 4 commits into from
Oct 21, 2024

Conversation

bgruening
Copy link
Member

No description provided.

Copy link

coderabbitai bot commented Oct 18, 2024

Walkthrough

The changes in the pull request focus on updating the bioconda_utils-requirements.txt file, specifically involving version modifications for several dependencies. The conda and conda-build versions have been increased from 24.5.* to 24.9.* and from 24.5.* to 24.7.*, respectively. The conda-index version has been raised from 0.4.* to 0.5.*, and the conda-package-streaming version has been updated from 0.9.* to 0.11.*. Additionally, the boa dependency has been commented out, indicating it is no longer necessary.

Other dependencies, including argh, colorlog, tqdm, yaspin, ruamel.yaml, pyaml, networkx, pandas, libblas, boltons, jsonschema, and jinja2, have not been altered. The anaconda-client, galaxy-tool-util, involucro, skopeo, findutils, and git dependencies also remain unchanged. The regex dependency has been specified with a version of 2024.*, while the backoff library is now set to 2.2.*. Other dependencies like gitpython, gidgethub, and pyjwt have not changed, with pyjwt requiring a minimum version of 2.4.0. The dependencies beautifulsoup4, requests, pygithub, diskcache, platformdirs, and tabulate remain unchanged.

Additionally, the versioneer.py file has undergone several modifications. The SafeConfigParser has been replaced with ConfigParser, affecting how configuration files are read. The error handling in the get_config_from_root function has been improved for clarity. The logic for retrieving version information has been streamlined, and the run_command function has been modified for better command execution and error reporting. Comments and documentation within the code have also been updated for clarity. The test/test_utils.py file has seen changes to import statements and exception handling to enhance error reporting during tests.


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
🪧 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.

@bgruening bgruening closed this Oct 18, 2024
@bgruening bgruening reopened this Oct 18, 2024
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a4560e5 and f3d1805.

📒 Files selected for processing (1)
  • versioneer.py (1 hunks)
🧰 Additional context used

versioneer.py Show resolved Hide resolved
@aliciaaevans
Copy link
Contributor

FAILED test/test_utils.py::test_rendering_sandboxing - conda_build.exceptions.CondaBuildUserError: Failed to render jinja template in /var/folders/4b/7k50gk0j4f5bjk3799wdt8nw0000gn/T/tmptggrcmcr/one/meta.yaml:
'GITHUB_TOKEN' is undefined

I think this is the cause: conda/conda-build#5371

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between aa0dc8d and 0ef7da9.

📒 Files selected for processing (1)
  • test/test_utils.py (2 hunks)
🧰 Additional context used
🪛 Ruff
test/test_utils.py

17-17: conda_build.api imported but unused

Remove unused import: conda_build.api

(F401)

🔇 Additional comments (1)
test/test_utils.py (1)

655-656: Improved exception handling

The change from SystemExit to exceptions.CondaBuildUserError is a good improvement. This modification provides more specific error handling for conda build processes.

This change offers the following benefits:

  1. It provides a more precise exception type, making it easier to distinguish between different error scenarios.
  2. It aligns with best practices by using a custom exception from the conda_build package, which is likely designed for this specific use case.
  3. It improves the overall error handling and debugging capabilities of the test suite.

test/test_utils.py Show resolved Hide resolved
@@ -652,7 +652,7 @@ def test_rendering_sandboxing():
assert ("'GITHUB_TOKEN' is undefined" in str(excinfo.value.stdout))
else:
# recipe for "one" should fail because GITHUB_TOKEN is not a jinja var.
with pytest.raises(SystemExit) as excinfo:
with pytest.raises(exceptions.CondaBuildUserError) as excinfo:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, we might need to update line 644 as well, if that behavior also changed.

@bgruening bgruening merged commit 167f348 into master Oct 21, 2024
10 checks passed
@bgruening bgruening deleted the update_deps_2024-10_less branch October 21, 2024 16:34
@bgruening
Copy link
Member Author

🙏

bgruening pushed a commit that referenced this pull request Oct 21, 2024
🤖 I have created a release \*beep\* \*boop\*
---
##
[3.4.0](https://www.github.com/bioconda/bioconda-utils/compare/v3.3.2...v3.4.0)
(2024-10-21)


### Features

* Update dependencies to latest versions - less complex
([#1011](https://www.github.com/bioconda/bioconda-utils/issues/1011))
([167f348](https://www.github.com/bioconda/bioconda-utils/commit/167f348724e77384859e54c23b5226f2e67a1975))
---


This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

2 participants