chore(deps): bump aiorwlock from 1.5.0 to 1.5.1 (#504) #442
fstrAnnotations
1 error and 1 warning
|
unit-tests
Github returned error "Resource not accessible by integration - https://docs.github.com/rest/commits/statuses#create-a-commit-status" when setting status on commit: 1b5b32002d651a5e61918f8e0376ccebc8c962d2
Request object:
{
"context": "unit test result",
"description": "",
"state": "success",
"owner": "firebolt-db",
"repo": "firebolt-python-sdk",
"sha": "1b5b32002d651a5e61918f8e0376ccebc8c962d2",
"target_url": "https://python.docs.firebolt.io//allure/_1b5b32002d651a5e61918f8e0376ccebc8c962d2_unit"
} Possible issues could be that the token used does not have access to the repository containing the commit or the commit/repository does not exist.
|
|
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: guibranco/github-status-action-v2@v1.1.13, peaceiris/actions-gh-pages@v4, schneegans/dynamic-badges-action@e9a478b16159b4d31420099ba146cdc50f134483. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pytest-coverage-report
Expired
|
9.58 KB |
sha256:52b5d2966d2111e90f8041cc846e84a6440f51fc3eb8c92460d82a87273797bf
|
|