[pre-commit.ci] pre-commit autoupdate

pre-commit-ci[bot] commented 1 month ago

updates:

Summary by Sourcery

Build:

Update pre-commit hooks to their latest versions, including validate-pyproject, pyupgrade, ruff-pre-commit, mirrors-mypy, blacken-docs, and typos.

semanticdiff-com[bot] commented 1 month ago

Review changes with SemanticDiff.

sourcery-ai[bot] commented 1 month ago

Reviewer's Guide by Sourcery

This PR updates several pre-commit hooks to their latest versions. The changes are implemented by updating the version numbers (rev) in the .pre-commit-config.yaml file for multiple development tools.

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

File-Level Changes

Change	Details	Files
Update pre-commit hook versions for code quality tools	Update validate-pyproject from v0.21 to v0.22 Update pyupgrade from v3.18.0 to v3.19.0 Update ruff from v0.7.0 to v0.7.1 Update mypy from v1.12.1 to v1.13.0 Update blacken-docs from 1.19.0 to 1.19.1 Update typos from v1.26.0 to v1.26.8	`.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](https://app.sourcery.ai) 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](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).

coderabbitai[bot] commented 1 month ago

[!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](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

what-the-diff[bot] commented 1 month ago

PR Summary

Updated validate-pyproject hook version The version of the validate-pyproject tool has been updated from v0.21 to v0.22. This should enhance the accuracy of our project validation.
Upgraded pyupgrade hook version We've updated the version of the pyupgrade tool from v3.18.0 to v3.19.0. This assists in keeping our Python code always at the cutting edge.
Boosted ruff hook version The ruff tool version has been upgraded from v0.7.0 to v0.7.1. This will make our processes more efficient.
Updated mypy hook version The mypy tool version has been updated from v1.12.1 to v1.13.0. This will enhance type-checking capabilities of our Python code.
Enhanced blacken-docs hook version The blacken-docs tool version is upgraded from 1.19.0 to 1.19.1 — this will improve the formatting in our documentation.
Improved typos hook version The typos tool version has been changed from v1.26.0 to v1.26.8. This update should increase our ability to detect and correct typos in codebase swiftly.

codiumai-pr-agent-free[bot] commented 1 month ago

CI Failure Feedback 🧐

(Checks updated until commit https://github.com/cleder/fastkml/commit/ddb0bc0381ee757335dabf9d2bb18d2b7b0510d3)

**Action:** static-tests (3.12)

**Failed stage:** [Linting](https://github.com/cleder/fastkml/actions/runs/11558574436/job/32171271833) [❌]

**Failure summary:** The action failed because the code formatting check identified that the file
transform_cascading_style.py in the examples directory would be reformatted. This indicates that the
file does not adhere to the required code style guidelines.

Relevant error logs:

```yaml 1: ##[group]Operating System 2: Ubuntu ... 331: Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.12.7/x64 332: Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.12.7/x64 333: Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.12.7/x64 334: LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.12.7/x64/lib 335: ##[endgroup] 336: would reformat /home/runner/work/fastkml/fastkml/examples/transform_cascading_style.py 337: Oh no! 💥 💔 💥 338: 1 file would be reformatted, 30 files would be left unchanged. 339: ##[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](https://pr-agent-docs.codium.ai/tools/ci_feedback/).

github-actions[bot] commented 1 month ago

Failed to generate code suggestions for PR

github-actions[bot] commented 1 month ago

Preparing review...

codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.71%. Comparing base (6fc70db) to head (ddb0bc0). Report is 2 commits behind head on develop.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #372 +/- ## ======================================== Coverage 98.71% 98.71% ======================================== Files 53 53 Lines 4894 4894 Branches 153 153 ======================================== Hits 4831 4831 Misses 48 48 Partials 15 15 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

cleder / fastkml