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

ci: skip py3.12 in test matrix #300

Merged
merged 1 commit into from
Jan 30, 2025
Merged

ci: skip py3.12 in test matrix #300

merged 1 commit into from
Jan 30, 2025

Conversation

aaronsteers
Copy link
Contributor

@aaronsteers aaronsteers commented Jan 30, 2025

Removing Py3.12 due to a concurrency issue / incompatibility in requests-cache library.

Raised by @tolik0 as blocker for:

cc @natikgadzhi, @bnchrch, @maxi297 for visibility

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflow configuration
    • Temporarily disabled Python 3.12 testing due to compatibility issues with a library

@github-actions github-actions bot added the ci label Jan 30, 2025
Copy link
Contributor

coderabbitai bot commented Jan 30, 2025

📝 Walkthrough

Walkthrough

The pull request modifies the GitHub Actions workflow configuration for pytest testing. Specifically, the Python version matrix in .github/workflows/pytest_matrix.yml has been updated by commenting out Python 3.12, effectively reducing the test matrix from three to two Python versions (3.10 and 3.11). This change appears to be due to a compatibility issue with the requests-cache library for Python 3.12.

Changes

File Change Summary
.github/workflows/pytest_matrix.yml Commented out Python 3.12 from the version matrix, leaving 3.10 and 3.11 active for testing

Possibly related PRs

Suggested labels

ci

Suggested reviewers

  • aldogonzalez8

Hey there! I noticed you've commented out Python 3.12 in the test matrix. Would you mind sharing a bit more context about the requests-cache blocker? It might be helpful to link the specific issue if possible, wdyt? 🤔 The change looks clean and straightforward, but a quick explanation could help future maintainers understand the reasoning behind the version exclusion.


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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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. (Beta)
  • @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.

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

🧹 Nitpick comments (1)
.github/workflows/pytest_matrix.yml (1)

33-33: LGTM! Clear documentation of the Python 3.12 exclusion.

The comment clearly explains why Python 3.12 is being excluded and provides a link to the relevant issue. This is great for maintainability! 🎯

Hey, would it make sense to add a TODO comment to track when we should re-enable Python 3.12 testing once the requests-cache blocker is resolved? Something like:

-            # "3.12",  # `requests-cache` blocker: https://github.com/airbytehq/airbyte-python-cdk/issues/299
+            # TODO: Re-enable Python 3.12 once requests-cache is compatible: https://github.com/airbytehq/airbyte-python-cdk/issues/299
+            # "3.12",

wdyt? 🤔

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4e7f94a and 3792b84.

📒 Files selected for processing (1)
  • .github/workflows/pytest_matrix.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Pytest (Fast)
🔇 Additional comments (1)
.github/workflows/pytest_matrix.yml (1)

33-33: Verify test coverage impact.

Let's check if removing Python 3.12 from the test matrix might impact our test coverage or miss any version-specific issues.

✅ Verification successful

Temporary removal of Python 3.12 testing is acceptable 👍

The codebase is explicitly configured to support Python versions up to 3.13, and the removal of Python 3.12 from the test matrix is purely due to a requests-cache dependency issue. No Python 3.12-specific code paths or features were found, and test coverage through Python 3.10 and 3.11 adequately covers the functionality. Once the requests-cache issue is resolved, Python 3.12 testing can be re-enabled without concerns.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for Python version specific imports or code paths

# Look for version checks or imports that might be specific to Python 3.12
echo "Searching for Python version specific code..."
rg -g '!.git' -g '*.py' "sys.version_info|python_version|@python_version|Python 3.12" .

# Look for potential compatibility imports that might need Python 3.12 testing
echo "Checking for compatibility imports..."
rg -g '!.git' -g '*.py' "from __future__ import|import typing|from typing import" .

Length of output: 40792


Script:

#!/bin/bash
# Check for any Python version requirements in setup files and requirements
echo "Checking setup.py and requirements files..."
find . -type f -name "setup.py" -o -name "requirements*.txt" -o -name "pyproject.toml" | xargs cat

# Check for any classifiers or Python version specifications
echo "Checking for Python version classifiers..."
find . -type f -name "setup.cfg" -o -name "setup.py" -o -name "pyproject.toml" | xargs grep -i "python_requires\|Programming Language :: Python\|requires-python"

Length of output: 9258

@aaronsteers aaronsteers requested a review from tolik0 January 30, 2025 17:00
@tolik0 tolik0 merged commit 0b14379 into main Jan 30, 2025
23 checks passed
@tolik0 tolik0 deleted the aj/skip-py312-tests-again branch January 30, 2025 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants