Skip to content

[concurrency] v0.5.2 — unified ConcurrencyGate — Tier 2 Item 5 / Python #11

[concurrency] v0.5.2 — unified ConcurrencyGate — Tier 2 Item 5 / Python

[concurrency] v0.5.2 — unified ConcurrencyGate — Tier 2 Item 5 / Python #11

Triggered via push May 27, 2026 07:29
Status Cancelled
Total duration 3m 57s
Artifacts

ci.yml

on: push
Lint (Ruff)
6s
Lint (Ruff)
Type Check (mypy)
14s
Type Check (mypy)
Dependency Security Audit
21s
Dependency Security Audit
Conformance Mark Coverage
8s
Conformance Mark Coverage
Matrix: Tests (pytest)
Fit to window
Zoom out
Zoom in

Annotations

25 errors and 6 warnings
ruff (UP035): src/iicp_client/iicp_tcp.py#L34
src/iicp_client/iicp_tcp.py:34:1: UP035 Import from `collections.abc` instead: `Awaitable`, `Callable` help: Import from `collections.abc`
ruff (UP017): src/iicp_client/conformance.py#L239
src/iicp_client/conformance.py:239:34: UP017 Use `datetime.UTC` alias help: Convert to `datetime.UTC` alias
ruff (B010): src/iicp_client/conformance.py#L221
src/iicp_client/conformance.py:221:9: B010 Do not call `setattr` with a constant attribute value. It is not any safer than normal property access. help: Replace `setattr` with assignment
ruff (E501): src/iicp_client/conformance.py#L152
src/iicp_client/conformance.py:152:101: E501 Line too long (114 > 100)
ruff (E501): src/iicp_client/conformance.py#L115
src/iicp_client/conformance.py:115:101: E501 Line too long (102 > 100)
ruff (E501): src/iicp_client/conformance.py#L100
src/iicp_client/conformance.py:100:101: E501 Line too long (106 > 100)
ruff (E501): src/iicp_client/concurrency.py#L58
src/iicp_client/concurrency.py:58:101: E501 Line too long (114 > 100)
ruff (E501): src/iicp_client/backends/openai_compat.py#L71
src/iicp_client/backends/openai_compat.py:71:101: E501 Line too long (109 > 100)
ruff (UP035): src/iicp_client/backends/openai_compat.py#L25
src/iicp_client/backends/openai_compat.py:25:1: UP035 Import from `collections.abc` instead: `Awaitable`, `Callable` help: Import from `collections.abc`
ruff (I001): src/iicp_client/__init__.py#L3
src/iicp_client/__init__.py:3:1: I001 Import block is un-sorted or un-formatted help: Organize imports
Conformance Mark Coverage
Process completed with exit code 1.
Type Check (mypy)
Process completed with exit code 1.
Tests (pytest) (3.11)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Tests (pytest) (3.11)
The operation was canceled.
Tests (pytest) (3.11)
Event loop stopped before Future completed.
Tests (pytest) (3.11)
Event loop stopped before Future completed.
Tests (pytest) (3.11)
Event loop stopped before Future completed.
Tests (pytest) (3.11)
Event loop stopped before Future completed.
Tests (pytest) (3.12)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Tests (pytest) (3.12)
The operation was canceled.
Tests (pytest) (3.12)
Event loop stopped before Future completed.
Tests (pytest) (3.12)
Event loop stopped before Future completed.
Tests (pytest) (3.12)
Event loop stopped before Future completed.
Tests (pytest) (3.12)
Event loop stopped before Future completed.
CI
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Lint (Ruff)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
Conformance Mark Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
Type Check (mypy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
Dependency Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
Tests (pytest) (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
Tests (pytest) (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/