[pre-commit.ci] pre-commit autoupdate #406

pre-commit-ci · 2025-01-06T16:42:10Z

updates:

Summary by Sourcery

Build:

Update pre-commit hooks to latest versions.

updates: - [github.com/astral-sh/ruff-pre-commit: v0.8.4 → v0.8.6](astral-sh/ruff-pre-commit@v0.8.4...v0.8.6) - [github.com/pre-commit/mirrors-mypy: v1.14.0 → v1.14.1](pre-commit/mirrors-mypy@v1.14.0...v1.14.1) - [github.com/crate-ci/typos: v1.28.4 → dictgen-v0.3.1](crate-ci/typos@v1.28.4...dictgen-v0.3.1)

semanticdiff-com · 2025-01-06T16:42:14Z

Review changes with

Changed Files

File	Status
tests/config_test.py	4% smaller
.pre-commit-config.yaml	Unsupported file format
fastkml/schema/xAL.xsd	Unsupported file format

sourcery-ai · 2025-01-06T16:42:15Z

Reviewer's Guide by Sourcery

This pull request updates the following pre-commit hooks: ruff from v0.8.4 to v0.8.6, mypy from v1.14.0 to v1.14.1, and typos from v1.28.4 to dictgen-v0.3.1.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated ruff-pre-commit from v0.8.4 to v0.8.6.	Updated the `rev` field for `ruff-pre-commit` from `v0.8.4` to `v0.8.6`.	`.pre-commit-config.yaml`
Updated mirrors-mypy from v1.14.0 to v1.14.1.	Updated the `rev` field for `mirrors-mypy` from `v1.14.0` to `v1.14.1`.	`.pre-commit-config.yaml`
Updated typos from v1.28.4 to dictgen-v0.3.1.	Updated the `rev` field for `typos` from `v1.28.4` to `dictgen-v0.3.1`.	`.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.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a 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. You can also use
this command to specify where the summary should be inserted.

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 · 2025-01-06T16:42:19Z

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

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.

sourcery-ai

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, pre-commit-ci[bot]!). We assume it knows what it's doing!

what-the-diff · 2025-01-06T16:42:43Z

PR Summary

Updated ruff-pre-commit tool
The ruff-pre-commit tool, which helps in automatically checking for any coding standard violations before the changes are committed, has been updated. The version has been upgraded from v0.8.4 to v0.8.6. This should provide us with better error detection capabilities and ensure higher code quality.
Upgraded mypy
Our mypy tool, a Python static type checker, has been upgraded from version v1.14.0 to v1.14.1. With this update, it should be more accurate and efficient in catching potential typing errors in our Python codebase.
Modified typos dependency
The dependency typos, previously at version v1.28.4, has been changed to dictgen-v0.3.1. It means that we are now using a different tool (or a different version of the tool) to handle typo checks in our code. This change should result in more efficient and accurate typo identification, hence reducing chances of errors caused by typos.

greptile-apps

PR Summary

Updates three pre-commit hooks in .pre-commit-config.yaml to newer versions, with the most notable change being the typos hook switching to a different versioning scheme.

Updated typos hook from v1.28.4 to dictgen-v0.3.1, representing a significant version scheme change
Bumped ruff-pre-commit from v0.8.4 to v0.8.6 for code formatting and linting
Updated mirrors-mypy from v1.14.0 to v1.14.1 for type checking

_{💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!}

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

for more information, see https://pre-commit.ci

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 contains only dependency version updates and generated files, requiring no automated code review

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

codiumai-pr-agent-free · 2025-01-06T16:46:38Z

CI Failure Feedback 🧐

(Checks updated until commit `48fa8f1`)

Action: cpython-lxml (3.8)
Failed stage: Test with pytest [❌]
Failed test name: test_fuzz_multi_track
Failure summary: The action failed in the hypothesis fuzz testing of MultiTrack objects. Specifically: Test `test_fuzz_multi_track` in `tests/hypothesis/gx_test.py` failed The failure occurred in the `assert_repr_roundtrip` function where the evaluated representation of a MultiTrack object did not match the original object The test involves complex KML/GX objects with datetime and timezone information Hypothesis spent over 5 minutes trying to shrink the failing example, indicating a complex failure case
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 294: tests/overlays_test.py ............................................ [ 81%] 295: tests/registry_test.py .... [ 82%] 296: tests/repr_eq_test.py ...... [ 83%] 297: tests/styles_test.py .............................................. [ 89%] 298: tests/times_test.py .................................................. [ 96%] 299: tests/utils_test.py ...... [ 96%] 300: tests/validator_test.py ........ [ 98%] 301: tests/views_test.py .............. [100%] 302: =================================== FAILURES =================================== ... 328: tests/hypothesis/gx_test.py:133: in test_fuzz_multi_track 329: assert_repr_roundtrip(multi_track) 330: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 331: obj = fastkml.gx.MultiTrack(ns='{http://www.google.com/kml/ext/2.2}', name_spaces={'kml': '{http://www.opengis.net/kml/2.2}'...=Point(0.0, 0.0), angle=Angle(heading=0.0, tilt=0.0, roll=0.0))], extended_data=None, {},)], interpolate=None, {},) 332: def assert_repr_roundtrip(obj: _XMLObject) -> None: 333: """Test that repr(obj) can be eval'd back to obj.""" 334: try: 335: > assert obj == eval(repr(obj), {}, eval_locals) # noqa: S307 336: E AssertionError ... 517: E dt=datetime.datetime(2001, 3, 18, 3, 0, tzinfo=tzfile('/usr/share/zoneinfo/NZ-CHAT')), 518: E resolution=None, 519: E ), 520: E )], 521: E )], 522: E interpolate=None, 523: E ) 524: E 525: E You can reproduce this example by temporarily adding @reproduce_failure('6.113.0', b'AXicY2BgZGJkZGCAISCBHTAynJM+fcpu3w+c8sg0TmNQQEPAgfaLhczL0QxiJE43NkcwaWoDKXEGvm+RUEcokGUQE9QR1kITTDQ/ngCy1qwPcb88/5sqyNjg3Yes+Fs9QAqO352TCrW7Ido5Vjjg1AxGxhhZoH4FRmZfaQYmJrA5WdrvJv6T/QJiXgg+e90w0oMYzygJMMgBGax/DjMwMYPMacxwUit0vFJCkl8YGVfzMjAyM2gz2M+ARHAv/wt9y7Prw1GVMbTf3lX/cP8NEKchcHd0ufjyUJC30ur/gwA8UKbWzplS/FpvIZB54ALRjmDYos/AxCcCT2rI4OLZuR8dutay4daNYhGqbsb9YOf9/4emoiGR7WEJc+5rkBfi3y99aDZvO5DZlOrBI/JT+xBQgSAkTLGD/0+TL72Z2ITTQYytIpDQ+NcCi2O8AE1FQyJTwlLbFxYoKsy0GBkEGZQ5neYy4nEa4/8L2I0MNvqwZL5lLYorK1WApIEV91QFYnIVONjcptyP7eT7hEOJBkb2ZERkMUYG1bTPvCk3t4ANCnIAiXHisowJIyIZ3q7M7rtXCSxhGLuX18/aszysHBKRUiwPM2W4MZwKAlsg/gQSpzyjN2pd/7wSt+8aXJuMK2bv2YXmDtwBw/hOxj3r55dydyILJLLLLbBm8ks9OIv9AiMTZa6g0A/4ahCiDKCg6A9iZBJkRggAACxYlbM=') as a decorator on your test case 526: tests/hypothesis/common.py:83: AssertionError 527: ---------------------------------- Hypothesis ---------------------------------- 528: WARNING: Hypothesis has spent more than five minutes working to shrink a failing example, and stopped because it is making very slow progress. When you re-run your tests, shrinking will resume and may take this long before aborting again. 529: PLEASE REPORT THIS if you can provide a reproducing example, so that we can improve shrinking performance for everyone. 530: ---------- coverage: platform linux, python 3.8.18-final-0 ----------- 531: Coverage XML written to file coverage.xml 532: Required test coverage of 95% reached. Total coverage: 100.00% 533: =========================== short test summary info ============================ 534: FAILED tests/hypothesis/gx_test.py::TestGx::test_fuzz_multi_track - AssertionError ... 714: when=KmlDateTime( 715: dt=datetime.datetime(2001, 3, 18, 3, 0, tzinfo=tzfile('/usr/share/zoneinfo/NZ-CHAT')), 716: resolution=None, 717: ), 718: )], 719: )], 720: interpolate=None, 721: ) 722: You can reproduce this example by temporarily adding @reproduce_failure('6.113.0', b'AXicY2BgZGJkZGCAISCBHTAynJM+fcpu3w+c8sg0TmNQQEPAgfaLhczL0QxiJE43NkcwaWoDKXEGvm+RUEcokGUQE9QR1kITTDQ/ngCy1qwPcb88/5sqyNjg3Yes+Fs9QAqO352TCrW7Ido5Vjjg1AxGxhhZoH4FRmZfaQYmJrA5WdrvJv6T/QJiXgg+e90w0oMYzygJMMgBGax/DjMwMYPMacxwUit0vFJCkl8YGVfzMjAyM2gz2M+ARHAv/wt9y7Prw1GVMbTf3lX/cP8NEKchcHd0ufjyUJC30ur/gwA8UKbWzplS/FpvIZB54ALRjmDYos/AxCcCT2rI4OLZuR8dutay4daNYhGqbsb9YOf9/4emoiGR7WEJc+5rkBfi3y99aDZvO5DZlOrBI/JT+xBQgSAkTLGD/0+TL72Z2ITTQYytIpDQ+NcCi2O8AE1FQyJTwlLbFxYoKsy0GBkEGZQ5neYy4nEa4/8L2I0MNvqwZL5lLYorK1WApIEV91QFYnIVONjcptyP7eT7hEOJBkb2ZERkMUYG1bTPvCk3t4ANCnIAiXHisowJIyIZ3q7M7rtXCSxhGLuX18/aszysHBKRUiwPM2W4MZwKAlsg/gQSpzyjN2pd/7wSt+8aXJuMK2bv2YXmDtwBw/hOxj3r55dydyILJLLLLbBm8ks9OIv9AiMTZa6g0A/4ahCiDKCg6A9iZBJkRggAACxYlbM=') as a decorator on your test case 723: ================== 1 failed, 729 passed in 552.50s (0:09:12) =================== 724: ##[error]Process completed with exit code 1.

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

github-actions · 2025-01-06T16:46:43Z

Preparing review...

github-actions · 2025-01-06T16:47:34Z

Failed to generate code suggestions for PR

github-actions · 2025-01-06T16:50:04Z

Preparing review...

sourcery-ai bot reviewed Jan 6, 2025

View reviewed changes

greptile-apps bot reviewed Jan 6, 2025

View reviewed changes

[pre-commit.ci] auto fixes from pre-commit.com hooks

48fa8f1

for more information, see https://pre-commit.ci

llamapreview bot reviewed Jan 6, 2025

View reviewed changes

cleder merged commit 8100a1c into develop Jan 6, 2025
54 of 56 checks passed

cleder deleted the pre-commit-ci-update-config branch January 6, 2025 16:54

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[pre-commit.ci] pre-commit autoupdate #406

[pre-commit.ci] pre-commit autoupdate #406

pre-commit-ci bot commented Jan 6, 2025 •

edited by sourcery-ai bot

Loading

semanticdiff-com bot commented Jan 6, 2025 •

edited

Loading

sourcery-ai bot commented Jan 6, 2025 •

edited

Loading

Interacting with Sourcery

Customizing Your Experience

Getting Help

coderabbitai bot commented Jan 6, 2025

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

Documentation and Community

sourcery-ai bot left a comment

what-the-diff bot commented Jan 6, 2025

greptile-apps bot left a comment

llamapreview bot left a comment

codiumai-pr-agent-free bot commented Jan 6, 2025 •

edited

Loading

Configuration options

github-actions bot commented Jan 6, 2025

github-actions bot commented Jan 6, 2025

github-actions bot commented Jan 6, 2025

[pre-commit.ci] pre-commit autoupdate #406

[pre-commit.ci] pre-commit autoupdate #406

Conversation

pre-commit-ci bot commented Jan 6, 2025 • edited by sourcery-ai bot Loading

Summary by Sourcery

semanticdiff-com bot commented Jan 6, 2025 • edited Loading

sourcery-ai bot commented Jan 6, 2025 • edited Loading

Reviewer's Guide by Sourcery

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

coderabbitai bot commented Jan 6, 2025

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

Documentation and Community

sourcery-ai bot left a comment

Choose a reason for hiding this comment

what-the-diff bot commented Jan 6, 2025

PR Summary

greptile-apps bot left a comment

Choose a reason for hiding this comment

PR Summary

llamapreview bot left a comment

Choose a reason for hiding this comment

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Analysis Result:

codiumai-pr-agent-free bot commented Jan 6, 2025 • edited Loading

CI Failure Feedback 🧐

(Checks updated until commit 48fa8f1)

Configuration options

github-actions bot commented Jan 6, 2025

github-actions bot commented Jan 6, 2025

github-actions bot commented Jan 6, 2025

pre-commit-ci bot commented Jan 6, 2025 •

edited by sourcery-ai bot

Loading

semanticdiff-com bot commented Jan 6, 2025 •

edited

Loading

sourcery-ai bot commented Jan 6, 2025 •

edited

Loading

codiumai-pr-agent-free bot commented Jan 6, 2025 •

edited

Loading

(Checks updated until commit `48fa8f1`)