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

chore: Fix jupyter failing test by using constraints #1093

Merged
merged 6 commits into from
Apr 12, 2024
Merged

Conversation

Czaki
Copy link
Collaborator

@Czaki Czaki commented Apr 2, 2024

Summary by CodeRabbit

  • Chores
    • Updated the Python version to 3.11 in the CI/CD pipeline.
    • Modified the path for the pip constraints file.
    • Introduced a new environment variable PIP_CONSTRAINT for specifying pip constraints.
    • Added Python 3.11 support to the test environment configurations in tox.ini.
    • Updated the jupyter dependency in the jupyter test environment configuration.
    • Removed an unnecessary line related to constraints for Python 3.9 in tox.ini.
    • Updated the pygments dependency version in the project configuration file.

@Czaki Czaki added this to the 0.15.3 milestone Apr 2, 2024
Copy link
Contributor

coderabbitai bot commented Apr 2, 2024

Walkthrough

This update ushers in a new chapter of configuration with Python 3.11, improving performance and embracing the latest features. It streamlines dependency management by updating paths, introducing the PIP_CONSTRAINT variable for constraint specification, and ensuring a more efficient and future-ready pipeline setup.

Changes

File Change Summary
azure-pipelines.yml, tox.ini, pyproject.toml Updated Python version to 3.11, adjusted dependencies, introduced PIP_CONSTRAINT variable, and updated pygments dependency to 2.12.0

🐇✨
In the realm of code, under the azure sky,
A rabbit hopped, with a twinkle in its eye.
"Python 3.11, oh how sleek,
With constraints so strong, no leak.
On pipelines we glide, with ease, we fly!"
🌟📦


Recent Review Details

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 398e063 and 489453a.
Files selected for processing (1)
  • pyproject.toml (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • pyproject.toml

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

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

@Czaki Czaki changed the title Fix jupyter failing test by using constraints maint: Fix jupyter failing test by using constraints Apr 2, 2024
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.

Hey @Czaki - I've reviewed your changes and they look great!

Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Docstrings: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

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.

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 293be19 and 22505c5.
Files selected for processing (1)
  • azure-pipelines.yml (1 hunks)
Additional comments not posted (3)
azure-pipelines.yml (3)

100-100: The Python version has been updated to 3.11 for the Notebook_check job. This change aligns with the PR's objective to address failing tests by ensuring compatibility with Python 3.11.


103-103: The path for the pip constraints file has been updated to requirements/constraints_py3.11.txt for the Notebook_check job. This update is crucial for ensuring that the correct versions of dependencies are used, which can help in resolving the failing tests issue.


110-111: The introduction of the PIP_CONSTRAINT environment variable with the value requirements/constraints_py3.11.txt is a significant addition. This variable explicitly specifies the constraints file to be used by pip during the dependency installation process, adding a layer of control over the versions of packages installed. This change is expected to reduce the likelihood of version conflicts that could lead to test failures.

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.

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 22505c5 and b586331.
Files selected for processing (3)
  • .azure-pipelines/tests.yaml (2 hunks)
  • azure-pipelines.yml (1 hunks)
  • tox.ini (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • azure-pipelines.yml
Additional comments not posted (5)
.azure-pipelines/tests.yaml (3)

6-6: The update to Python 3.11 is correctly specified in the UsePythonVersion task. This change aligns with the PR objectives to ensure compatibility with Python 3.11.


9-9: The pip constraints file path is correctly updated to constraints_py3.11.txt, ensuring that the correct dependencies are used for Python 3.11. However, there's a potential inconsistency in the PIP_CONSTRAINT environment variable setting.

Please verify that the PIP_CONSTRAINT environment variable in the "Run Tox" script step should also reference constraints_py3.11.txt instead of constraints_py3.9.txt to align with the Python 3.11 update.


19-19: The tox environment name is updated to py311-PyQt5-azure, which correctly reflects the new Python version. However, ensure that all references to the tox environment throughout the project are updated accordingly.

tox.ini (2)

104-104: Adding Python 3.11 support in the testenv configurations is a necessary update that aligns with the PR objectives. This change ensures that tests can run against the latest Python version.


113-113: The update to include the jupyter dependency in the testenv:jupyter environment is appropriate for ensuring that Jupyter notebooks can be tested correctly. However, it's important to verify that the matplotlib dependency is also required for the Jupyter environment to function as intended.

Please confirm that the matplotlib dependency is necessary for the Jupyter test environment. If it is not required, consider removing it to streamline the dependencies.

@Czaki Czaki changed the title maint: Fix jupyter failing test by using constraints chore: Fix jupyter failing test by using constraints Apr 2, 2024
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.

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between b586331 and fd3458a.
Files selected for processing (1)
  • tox.ini (3 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tox.ini

Copy link

sonarcloud bot commented Apr 12, 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

codecov bot commented Apr 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.83%. Comparing base (293be19) to head (489453a).
Report is 85 commits behind head on develop.

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

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

@Czaki Czaki merged commit a42ed79 into develop Apr 12, 2024
50 of 55 checks passed
@Czaki Czaki deleted the fix_jupyter_test branch April 12, 2024 10:33
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