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

test: [Automatic] Constraints upgrades: psygnal, pydantic, sentry-sdk, vispy #1090

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

Czaki
Copy link
Collaborator

@Czaki Czaki commented Mar 18, 2024

This PR is automatically created and updated by PartSeg GitHub
action cron to keep bundle dependencies modules up to date.

The updated packages are:

  • comm
  • coverage
  • dask
  • docstring-parser
  • fsspec
  • jupyter-client
  • jupyter-core
  • psygnal
  • pydantic
  • referencing
  • sentry-sdk
  • setuptools
  • traitlets
  • vispy
  • zipp

Summary by CodeRabbit

  • Chores
    • Updated dependencies across various Python versions to enhance performance and security.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • We don't currently review documentation changes - Let us know if you'd like us to change this.
  • We don't currently review these file types ['.txt'] - Let us know if you'd like us to change this.

Copy link
Contributor

coderabbitai bot commented Mar 18, 2024

Walkthrough

The recent updates involve several Python package upgrades across different Python versions, enhancing functionality, security, and compatibility. Key updates include comm, coverage, dask, and others, ensuring improved performance and bug fixes. These changes are applied to both general and Pydantic-specific requirements, maintaining consistency across environments.

Changes

Files Change Summary
requirements/constraints_py3.8.txt, ...py3.9.txt, ...py3.10.txt, ...py3.11.txt Packages like comm, coverage, dask, docstring-parser, and more updated.
requirements/constraints_py3.8_pydantic_1.txt, ...py3.9_pydantic_1.txt, ...py3.10_pydantic_1.txt, ...py3.11_pydantic_1.txt Similar updates as above but tailored for Pydantic 1 environments.

🐇✨
In the garden of code, where the Python snakes roam,
Updates bloom like flowers, in their digital home.
From comm to coverage, dask in the light,
Each package now polished, more robust and bright.
Oh, how the versions, from old to the new,
Bring joy to the coder, and the CodeRabbit too!
🌼🐾

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>.
    • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

sonarcloud bot commented Mar 18, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

Copy link
Contributor

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

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 488fd5e and 8a5ebc1.
Files selected for processing (9)
  • requirements/constraints_py3.10.txt (10 hunks)
  • requirements/constraints_py3.10_pydantic_1.txt (9 hunks)
  • requirements/constraints_py3.11.txt (10 hunks)
  • requirements/constraints_py3.11_docs.txt (10 hunks)
  • requirements/constraints_py3.11_pydantic_1.txt (9 hunks)
  • requirements/constraints_py3.8.txt (12 hunks)
  • requirements/constraints_py3.8_pydantic_1.txt (11 hunks)
  • requirements/constraints_py3.9.txt (10 hunks)
  • requirements/constraints_py3.9_pydantic_1.txt (9 hunks)
Additional comments: 128
requirements/constraints_py3.11_docs.txt (13)
  • 39-39: The package comm has been updated to version 0.2.2. Ensure this version is compatible with the project's usage of comm, especially since it's a dependency of ipykernel.
  • 42-42: The update of dask to version 2024.3.1 is significant for parallel computing capabilities. Verify that this version does not introduce breaking changes or performance regressions in the project's data processing workflows.
  • 49-49: The update of docstring-parser to version 0.16 could impact how documentation is generated or interpreted. Confirm that this version aligns with the project's documentation standards and practices.
  • 62-62: The update of fsspec to version 2024.3.0 is crucial for file system operations. It's important to ensure that this version maintains compatibility with dask and other data processing tools used in the project.
  • 101-101: The update of jupyter-client to version 8.6.1 should be checked for compatibility with the project's Jupyter ecosystem, including kernels and notebook extensions.
  • 105-105: Updating jupyter-core to version 5.7.2 could affect the core functionalities of Jupyter in the project. Verify that this update does not disrupt the project's Jupyter-based workflows or integrations.
  • 213-213: The update of psygnal to version 0.10.2 might influence signal handling in the project. Ensure that this version is compatible with the project's event-driven components.
  • 225-225: The update of pydantic to version 2.6.4 is critical for data validation and settings management. Confirm that this version supports the project's data models and configuration management without issues.
  • 298-298: The update of referencing to version 0.34.0 could impact how references are managed within the project. Verify that this version aligns with the project's reference management practices.
  • 319-319: The update of sentry-sdk to version 1.42.0 is important for error tracking and monitoring. Ensure that this version integrates smoothly with the project's error handling and reporting mechanisms.
  • 383-383: Updating traitlets to version 5.14.2 could affect configuration management across the project. It's crucial to verify that this version is compatible with the project's use of Jupyter and other components relying on traitlets.
  • 410-410: The update of vispy to version 0.14.2 is significant for graphical rendering. Confirm that this version enhances the project's visualization capabilities without introducing regressions.
  • 420-420: The update of zipp to version 3.18.1 might influence how archive files are handled. Ensure that this version is compatible with the project's packaging and distribution workflows.
requirements/constraints_py3.11_pydantic_1.txt (13)
  • 38-38: The update to comm==0.2.2 seems appropriate, but ensure compatibility with ipykernel and other dependent packages.
  • 40-40: coverage==7.4.4 update is noted. Verify that this version does not introduce any breaking changes to your test suite or coverage reporting.
  • 42-42: The dask==2024.3.1 version update should be checked for compatibility with napari and other parallel computing workflows you have.
  • 49-49: Ensure docstring-parser==0.16 does not affect any documentation generation tools or processes you use.
  • 60-60: The update to fsspec==2024.3.0 should be compatible with dask's updated version and any custom file system operations.
  • 101-101: jupyter-client==8.6.1 and jupyter-core==5.7.2 updates should be verified for compatibility with your Jupyter ecosystem, including notebooks and kernels.
  • 105-105: ,
  • 221-221: Check psygnal==0.10.2 for any signal handling changes that might affect app-model, magicgui, napari, and npe2.
  • 308-308: referencing==0.34.0 update should be reviewed for any impact on jsonschema and jsonschema-specifications integrations.
  • 329-329: setuptools==69.2.0 is a core dependency. Ensure this update does not impact your build or deployment processes.
  • 391-391: traitlets==5.14.2 update should be checked for compatibility with IPython, Jupyter, and other components that rely on it.
  • 417-417: Verify vispy==0.14.2 for compatibility with napari's graphical rendering requirements.
  • 427-427: zipp==3.18.1 update should not impact the functionality of importlib-metadata. However, verify to ensure smooth integration.
requirements/constraints_py3.11.txt (15)
  • 40-40: The update for comm from 0.2.1 to 0.2.2 is noted.
  • 42-42: The update for coverage from 7.4.3 to 7.4.4 is noted.
  • 44-44: The update for dask from 2024.2.1 to 2024.3.1 is noted.
  • 51-51: The update for docstring-parser from 0.15 to 0.16 is noted.
  • 62-62: The update for fsspec from 2024.2.0 to 2024.3.0 is noted.
  • 103-103: The update for jupyter-client from 8.6.0 to 8.6.1 is noted.
  • 107-107: The update for jupyter-core from 5.7.1 to 5.7.2 is noted.
  • 223-223: The update for psygnal from 0.10.0 to 0.10.2 is noted.
  • 235-235: The update for pydantic from 2.6.3 to 2.6.4 is noted.
  • 312-312: The update for referencing from 0.33.0 to 0.34.0 is noted.
  • 333-333: The update for sentry-sdk from 1.41.0 to 1.42.0 is noted.
  • 334-334: The update for setuptools from 69.1.1 to 69.2.0 is noted.
  • 395-395: The update for traitlets from 5.14.1 to 5.14.2 is noted.
  • 422-422: The update for vispy from 0.14.1 to 0.14.2 is noted.
  • 432-432: The update for zipp from 3.17.0 to 3.18.1 is noted.
requirements/constraints_py3.10_pydantic_1.txt (14)
  • 38-38: The package comm has been updated to version 0.2.2. Ensure this version is compatible with the project's requirements and does not introduce breaking changes.
  • 40-40: The coverage package has been updated to version 7.4.4. It's important to verify that this update does not affect the project's test coverage reporting.
  • 42-42: The update to dask version 2024.3.1 could introduce significant changes given the major version jump. Confirm compatibility with existing parallel computing workflows.
  • 49-49: Updating docstring-parser to version 0.16 may affect documentation generation. Ensure that the new version is compatible with the project's documentation standards.
  • 64-64: The update to fsspec version 2024.3.0 is crucial for file system operations. Verify that this update integrates well with the project's data handling mechanisms.
  • 107-107: The jupyter-client package has been updated to version 8.6.1. Given its role in the Jupyter ecosystem, ensure that this update does not disrupt interactive computing environments.
  • 111-111: Updating jupyter-core to version 5.7.2 could impact the core functionalities of Jupyter notebooks. Confirm that the update is seamless and does not affect notebook operations.
  • 227-227: The update to psygnal version 0.10.2 might influence signal handling in the application. Verify that the updated version maintains expected functionality.
  • 314-314: The referencing package update to version 0.34.0 could affect reference management within the software. Ensure compatibility with the project's reference handling mechanisms.
  • 335-335: The sentry-sdk package has been updated to version 1.42.0. Confirm that this update does not interfere with error reporting and monitoring functionalities.
  • 336-336: Updating setuptools to version 69.2.0 is critical for the build process. Verify that this update does not disrupt package building and distribution.
  • 404-404: The update to traitlets version 5.14.2 could impact configuration management. Ensure that this update is compatible with the project's configuration handling.
  • 430-430: The vispy package has been updated to version 0.14.2. Given its role in graphical rendering, confirm that this update enhances the software's graphical capabilities without introducing issues.
  • 440-440: Updating zipp to version 3.18.1 might influence archive handling and importlib metadata. Verify compatibility with the project's archive management.
requirements/constraints_py3.10.txt (15)
  • 40-40: The update of comm from 0.2.1 to 0.2.2 is noted. Ensure compatibility with ipykernel.
  • 42-42: The minor patch update for coverage to 7.4.4 is appropriate for maintaining test coverage reliability.
  • 44-44: Updating dask to 2024.3.1 supports enhanced parallel computing capabilities. Verify integration with napari.
  • 51-51: The update of docstring-parser to version 0.16 should improve documentation parsing capabilities. Check compatibility with magicgui.
  • 66-66: The fsspec update to 2024.3.0 is crucial for file system operations. Ensure it integrates well with dask.
  • 109-109: The minor update to jupyter-client enhances Jupyter ecosystem integration. Confirm compatibility with ipykernel and qtconsole.
  • 113-113: Updating jupyter-core to 5.7.2 is beneficial for core Jupyter functionalities. Verify its impact on ipykernel, jupyter-client, and qtconsole.
  • 229-229: The update of psygnal to 0.10.2 enhances signal handling. Check its integration with app-model, magicgui, napari, and npe2.
  • 241-241: pydantic version 2.6.4 update supports robust data validation. Ensure compatibility with app-model, napari, npe2, and pydantic-compat.
  • 318-318: The minor update for referencing to 0.34.0 may improve reference management. Confirm its integration with jsonschema and jsonschema-specifications.
  • 339-339: Updating sentry-sdk to 1.42.0 enhances error tracking capabilities. Ensure it does not affect error reporting in napari.
  • 340-340: The setuptools update to 69.2.0 is crucial for package management. Verify its compatibility with pyinstaller and pyinstaller-hooks-contrib.
  • 408-408: Updating traitlets to 5.14.2 supports enhanced configuration management. Check its impact on comm, ipykernel, ipython, jupyter-client, and jupyter-core.
  • 435-435: The vispy update to 0.14.2 enhances graphical rendering capabilities. Ensure compatibility with napari and napari-svg.
  • 445-445: Updating zipp to 3.18.1 supports improved archive handling. Confirm its integration with importlib-metadata.
requirements/constraints_py3.9_pydantic_1.txt (14)
  • 38-38: The package comm has been updated to version 0.2.2. Ensure this version is compatible with other dependencies and the project's Python version.
  • 40-40: The coverage package is updated to version 7.4.4. It's important to verify that this version does not introduce any breaking changes affecting the project's test coverage reporting.
  • 42-42: dask version 2024.3.1 is specified. Given the significant role of Dask in parallel computing within projects, ensure this update integrates well with the project's existing parallel computation workflows.
  • 49-49: The update to docstring-parser version 0.16 should be checked for compatibility with the project's documentation generation tools.
  • 64-64: fsspec version 2024.3.0 is updated. Confirm that this version is compatible with Dask's updated version, as fsspec is often used in conjunction with Dask for handling file systems.
  • 111-111: jupyter-client has been updated to version 8.6.1. Ensure that this update does not affect the project's Jupyter notebook integration, especially in terms of kernel management and communication.
  • 115-115: The update to jupyter-core version 5.7.2 should be verified for compatibility with jupyter-client and other Jupyter ecosystem packages.
  • 231-231: psygnal version 0.10.2 is updated. Given its role in signal handling, ensure that this update does not introduce any regressions in event-driven parts of the project.
  • 318-318: The update to referencing version 0.34.0 should be checked for compatibility with jsonschema and other packages that may rely on referencing capabilities.
  • 339-339: sentry-sdk version 1.42.0 is updated. Verify that this version integrates smoothly with the project's error reporting and monitoring setup.
  • 340-340: setuptools version 69.2.0 is updated. It's crucial to ensure that this foundational package's update does not impact the build and distribution process of the project.
  • 408-408: traitlets version 5.14.2 is updated. Given its widespread use in configuration management across Jupyter and IPython projects, ensure this update is compatible with those dependencies.
  • 435-435: vispy version 0.14.2 is updated. As a high-performance graphics library, verify that this update enhances the project's graphical rendering capabilities without introducing regressions.
  • 445-445: The update to zipp version 3.18.1 should be checked for compatibility with importlib-metadata and other packages relying on archive handling and metadata inspection.
requirements/constraints_py3.9.txt (15)
  • 40-40: Updated comm from 0.2.1 to 0.2.2.
  • 42-42: Updated coverage from 7.4.3 to 7.4.4.
  • 44-44: Updated dask from 2024.2.1 to 2024.3.1.
  • 51-51: Updated docstring-parser from 0.15 to 0.16.
  • 66-66: Updated fsspec from 2024.2.0 to 2024.3.0.
  • 113-113: Updated jupyter-client from 8.6.0 to 8.6.1.
  • 117-117: Updated jupyter-core from 5.7.1 to 5.7.2.
  • 233-233: Updated psygnal from 0.10.0 to 0.10.2.
  • 245-245: Updated pydantic from 2.6.3 to 2.6.4.
  • 322-322: Updated referencing from 0.33.0 to 0.34.0.
  • 343-343: Updated sentry-sdk from 1.41.0 to 1.42.0.
  • 344-344: Updated setuptools from 69.1.1 to 69.2.0.
  • 412-412: Updated traitlets from 5.14.1 to 5.14.2.
  • 440-440: Updated vispy from 0.14.1 to 0.14.2.
  • 450-450: Updated zipp from 3.17.0 to 3.18.1.
requirements/constraints_py3.8_pydantic_1.txt (14)
  • 40-40: Ensure compatibility and test the updated comm package version 0.2.2 with dependent components, especially those interacting with ipykernel.
  • 42-42: The update to coverage==7.4.4 is noted. Verify that this version is compatible with your CI/CD pipeline and does not introduce any breaking changes in coverage reporting.
  • 51-51: docstring-parser version 0.16 should be tested for compatibility with existing documentation generation workflows.
  • 64-64: The update to fsspec==2024.3.0 is significant for Dask-related operations. Ensure that this version works seamlessly with your Dask workflows.
  • 89-89: importlib-resources version 6.3.1 update should be checked for compatibility with projects using jsonschema and vispy.
  • 116-116: Updating jupyter-client to 8.6.1 may affect Jupyter notebook interactions. Confirm that this update integrates well with your Jupyter ecosystem.
  • 120-120: Ensure jupyter-core==5.7.2 update does not impact the functionality of Jupyter-based applications.
  • 241-241: The update to psygnal==0.10.2 should be tested for signal handling in GUI components, especially with napari and magicgui.
  • 332-332: Verify that the update to referencing==0.34.0 does not impact JSON schema validations or specifications.
  • 353-353: The sentry-sdk==1.42.0 update should be verified for error reporting functionality in production environments.
  • 354-354: Confirm that setuptools==69.2.0 is compatible with your build and deployment processes.
  • 422-422: Ensure traitlets==5.14.2 update does not introduce issues with configuration management in Jupyter and IPython environments.
  • 449-449: The update to vispy==0.14.2 should be thoroughly tested for graphical rendering performance and compatibility with napari.
  • 459-459: Check compatibility of zipp==3.18.1 with importlib-metadata and importlib-resources to ensure smooth package management.
requirements/constraints_py3.8.txt (15)
  • 42-42: The update of comm from 0.2.1 to 0.2.2 is noted and appears correct.
  • 44-44: The update of coverage from 7.4.3 to 7.4.4 is correct and likely includes minor fixes or improvements.
  • 53-53: Updating docstring-parser from 0.15 to 0.16 should bring enhancements or bug fixes without breaking changes.
  • 66-66: The update of fsspec from 2024.2.0 to 2024.3.0 is correct. Ensure compatibility with dask and other dependent packages.
  • 91-91: importlib-resources updated from 6.1.3 to 6.3.1. This is a significant jump; ensure no breaking changes affect the project.
  • 118-118: The minor update of jupyter-client from 8.6.0 to 8.6.1 should be safe, focusing on bug fixes or minor improvements.
  • 122-122: Updating jupyter-core from 5.7.1 to 5.7.2 is approved. It's a minor update likely addressing bug fixes.
  • 243-243: psygnal updated from 0.10.0 to 0.10.2. Given its use in signaling, ensure no API changes disrupt existing functionality.
  • 255-255: The update of pydantic from 2.6.3 to 2.6.4 is approved. Check for any deprecated features or significant changes in behavior.
  • 336-336: referencing updated from 0.33.0 to 0.34.0. Verify that the update does not affect any schema or reference management negatively.
  • 357-357: Updating sentry-sdk from 1.41.0 to 1.42.0 is approved. Ensure that error reporting and logging functionalities are unaffected.
  • 358-358: The update of setuptools from 69.1.1 to 69.2.0 is correct. This is a foundational package; ensure no build or deployment issues arise.
  • 426-426: traitlets updated from 5.14.1 to 5.14.2. This package is often used for configuration; ensure no breaking changes in configurations.
  • 455-455: The update of vispy from 0.14.1 to 0.14.2 is approved. Given its role in graphical rendering, test graphical outputs for any unexpected changes.
  • 465-465: Updating zipp from 3.17.0 to 3.18.1 is approved. This package is often a dependency of other packages; ensure no compatibility issues.

Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.81%. Comparing base (488fd5e) to head (8a5ebc1).
Report is 86 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1090      +/-   ##
===========================================
- Coverage    92.83%   92.81%   -0.02%     
===========================================
  Files          205      205              
  Lines        32469    32469              
===========================================
- Hits         30142    30137       -5     
- Misses        2327     2332       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Czaki Czaki added this to the 0.15.3 milestone Mar 18, 2024
@Czaki Czaki merged commit 293be19 into develop Mar 18, 2024
50 checks passed
@Czaki Czaki deleted the auto-dependency-upgrades branch March 18, 2024 10:48
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