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

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Aug 12, 2024

Copy link

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 9263b76 to 0bd8288 Compare September 16, 2024 20:01
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 0bd8288 to 3b76987 Compare October 7, 2024 21:09
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 3b76987 to 6bd7ca4 Compare October 21, 2024 20:18
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 6bd7ca4 to d0e1cd8 Compare October 28, 2024 20:30
Copy link

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from d0e1cd8 to 2801ad7 Compare November 4, 2024 20:25
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 81ef197 to 1a22b86 Compare December 30, 2024 19:46
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 6bf2058 to 22cf3bc Compare January 20, 2025 20:06
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 22cf3bc to d54f059 Compare January 27, 2025 20:16
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from d54f059 to b21ee4e Compare February 3, 2025 20:41
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 623c709 to 54b3d68 Compare February 24, 2025 18:08
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 54b3d68 to 85fc3a3 Compare March 10, 2025 18:14
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 85fc3a3 to 479a38e Compare March 17, 2025 18:17
updates:
- [github.com/gitleaks/gitleaks: v8.21.2 → v8.24.2](gitleaks/gitleaks@v8.21.2...v8.24.2)
- https://github.com/google/osv-scanner/: v1.9.1 → v2.0.0
- [github.com/pre-commit/pre-commit-hooks: v4.6.0 → v5.0.0](pre-commit/pre-commit-hooks@v4.6.0...v5.0.0)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 479a38e to 07a2991 Compare March 24, 2025 18:12
Copy link

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

CI Feedback 🧐

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

Action: sonarcloud

Failed stage: Run mise run dev:lint --no-fail [❌]

Failure summary:

The action failed because the GitHub runner received a shutdown signal during the execution of the
dev:lint task. The runner was terminated before the task could complete, resulting in exit code 143.
This is typically caused by:

  • The runner service being stopped
  • A manually started runner being canceled
  • Possible timeout or infrastructure issue on GitHub's side

    The actual lint task didn't complete its execution, so there's no information about any code issues
    that might exist.

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    243:  ##[endgroup]
    244:  ##[group]Running mise install 
    245:  [command]/home/runner/.local/share/mise/bin/mise install
    246:  �[2mmise�[0m all runtimes are installed
    247:  ##[endgroup]
    248:  ##[group]Run mise run dev:lint --no-fail
    249:  �[36;1mmise run dev:lint --no-fail�[0m
    250:  shell: /usr/bin/bash -e {0}
    251:  env:
    252:  MISE_EXPERIMENTAL: 1
    253:  MISE_LOG_LEVEL: info
    254:  MISE_TRUSTED_CONFIG_PATHS: /home/runner/work/sophrosyne/sophrosyne
    255:  MISE_YES: 1
    256:  ##[endgroup]
    257:  �[0m�[34m[dev:lint]�[0m �[1m$ ~/work/sophrosyne/sophrosyne/.mise/tasks/dev/lint --no-fail�[0m
    258:  �[0m�[34m[dev:lint]�[0m �[31mERROR�[0m ~/work/sophrosyne/sophrosyne/.mise/tasks/dev/lint exited with non-zero status: no exit status
    259:  �[0m�[34m[dev:lint]�[0m �[31mERROR�[0m task failed
    260:  ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
    261:  ##[error]Process completed with exit code 143.
    262:  Cleaning up orphan processes
    

    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.

    0 participants