[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.11.10 → v0.11.13
• github.com/pre-commit/mirrors-mypy: v1.15.0 → v1.16.0

Summary by Sourcery

CI:

• Bump ruff-pre-commit hook from v0.11.10 to v0.11.11

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.pre-commit-config.yaml	0% smaller

[sourcery-ai]

Reviewer's Guide

This PR updates the ruff-pre-commit hook in the project’s pre-commit configuration to the latest patch release (v0.11.11).

File-Level Changes

Change	Details	Files
Bump ruff-pre-commit hook version	Changed rev from v0.11.10 to v0.11.11	.pre-commit-config.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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.

[codiumai-pr-agent-free]

CI Feedback 🧐

(Feedback updated until commit 62ac14a)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: cpython (3.13)

Failed stage: Test with pytest [❌]

Failed test name: test_diff, test_remove_diff

Failure summary: The action failed because two tests failed: 1. test_diff (line 222-235): Expected the command output to have 14 lines but got an empty string. The test expected result.stdout.splitlines() to have 14 lines, but result.stdout was empty. 2. test_remove_diff (line 236-249): Same issue as above - expected the command output to have 14 lines but got an empty string. Both failures indicate that the --diff flag for the commands crepr add and crepr remove is not producing any output, when it should be showing diff information with 14 lines.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 206: env: 207: pythonLocation: /opt/hostedtoolcache/Python/3.13.3/x64 208: PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.13.3/x64/lib/pkgconfig 209: Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.3/x64 210: Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.3/x64 211: Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.3/x64 212: LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.13.3/x64/lib 213: ##[endgroup] 214: ============================= test session starts ============================== 215: platform linux -- Python 3.13.3, pytest-8.3.5, pluggy-1.6.0 216: rootdir: /home/runner/work/crepr/crepr 217: configfile: pyproject.toml 218: plugins: cov-6.1.1 219: collected 30 items 220: tests/run_test.py ....................F..F...... [100%] 221: =================================== FAILURES =================================== 222: __________________________________ test_diff ___________________________________ 223: def test_diff() -> None: 224: """Print the diff.""" 225: path = test_dir / "classes" / "kw_only_test.py" 226: filename = str(path.absolute()) 227: result = runner.invoke(crepr.app, ["add", "--diff", filename]) 228: assert result.exit_code == 0 229: > assert len(result.stdout.splitlines()) == 14 230: E AssertionError: assert 0 == 14 231: E + where 0 = len([]) 232: E + where [] = <built-in method splitlines of str object at 0x7f1a8a503ac8>() 233: E + where <built-in method splitlines of str object at 0x7f1a8a503ac8> = ''.splitlines 234: E + where '' = <Result okay>.stdout 235: tests/run_test.py:254: AssertionError 236: _______________________________ test_remove_diff _______________________________ 237: def test_remove_diff() -> None: 238: """Remove the changes.""" 239: path = test_dir / "remove" / "kw_only_test.py" 240: file_name = str(path.absolute()) 241: result = runner.invoke(crepr.app, ["remove", "--diff", file_name]) 242: assert result.exit_code == 0 243: > assert len(result.stdout.splitlines()) == 14 244: E AssertionError: assert 0 == 14 245: E + where 0 = len([]) 246: E + where [] = <built-in method splitlines of str object at 0x7f1a8a503ac8>() 247: E + where <built-in method splitlines of str object at 0x7f1a8a503ac8> = ''.splitlines 248: E + where '' = <Result okay>.stdout 249: tests/run_test.py:306: AssertionError 250: =============================== warnings summary =============================== ... 252: /home/runner/work/crepr/crepr/tests/classes/existing_repr_test.py:27: PytestCollectionWarning: cannot collect test class 'TestDataClass' because it has a __init__ constructor (from: tests/classes/existing_repr_test.py) 253: @dataclasses.dataclass 254: tests/classes/existing_repr_test.py:34 255: /home/runner/work/crepr/crepr/tests/classes/existing_repr_test.py:34: PytestCollectionWarning: cannot collect test class 'TestDataClassFrozen' because it has a __init__ constructor (from: tests/classes/existing_repr_test.py) 256: @dataclasses.dataclass(frozen=True) 257: ../../../../../opt/hostedtoolcache/Python/3.13.3/x64/lib/python3.13/site-packages/typer/params.py:206 258: /opt/hostedtoolcache/Python/3.13.3/x64/lib/python3.13/site-packages/typer/params.py:206: DeprecationWarning: The 'is_flag' and 'flag_value' parameters are not supported by Typer and will be removed entirely in a future release. 259: return OptionInfo( 260: tests/run_test.py: 30 warnings 261: <frozen importlib._bootstrap>:530: DeprecationWarning: the load_module() method is deprecated and slated for removal in Python 3.15; use exec_module() instead 262: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 263: ================================ tests coverage ================================ 264: _______________ coverage: platform linux, python 3.13.3-final-0 ________________ 265: Coverage XML written to file coverage.xml 266: =========================== short test summary info ============================ 267: FAILED tests/run_test.py::test_diff - AssertionError: assert 0 == 14 268: + where 0 = len([]) 269: + where [] = <built-in method splitlines of str object at 0x7f1a8a503ac8>() 270: + where <built-in method splitlines of str object at 0x7f1a8a503ac8> = ''.splitlines 271: + where '' = <Result okay>.stdout 272: FAILED tests/run_test.py::test_remove_diff - AssertionError: assert 0 == 14 273: + where 0 = len([]) 274: + where [] = <built-in method splitlines of str object at 0x7f1a8a503ac8>() 275: + where <built-in method splitlines of str object at 0x7f1a8a503ac8> = ''.splitlines 276: + where '' = <Result okay>.stdout 277: ================== 2 failed, 28 passed, 33 warnings in 0.55s =================== 278: ##[error]Process completed with exit code 1. 279: Post job cleanup.

[greptile-apps]

PR Summary

Updates the ruff-pre-commit hook from v0.11.10 to v0.11.11 in .pre-commit-config.yaml, a minor patch update for improved linting capabilities.

• Updated astral-sh/ruff-pre-commit hook version in .pre-commit-config.yaml from v0.11.10 to v0.11.11

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR only contains version updates and formatting changes

Technical Context:

Version and formatting changes detected, which include:

• Package version updates
• Dependency version changes
• Code formatting adjustments
• Whitespace modifications
• Structural formatting changes

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team