Process completed with exit code 2.

The job was canceled because "_3_10" failed.

Process completed with exit code 2.

The job was canceled because "_3_10" failed.

The operation was canceled.

The operation was canceled.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, pre-commit/[email protected], actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, pre-commit/[email protected], actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/279/merge, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-d60b3d49f376f2eab33383f419de958bd3169b07292e84c00402f8307e7c6048, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, pre-commit/[email protected], actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/279/merge, Key: pre-commit-2-9c5c819fc89c329ca97813f568aa5438bf6b4c15f2f88679042da30455896652-d60b3d49f376f2eab33383f419de958bd3169b07292e84c00402f8307e7c6048, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.