Skip to content

fix: Use same client_key for Actor created request_queue and improve its metadata estimation #624

fix: Use same client_key for Actor created request_queue and improve its metadata estimation

fix: Use same client_key for Actor created request_queue and improve its metadata estimation #624

Triggered via pull request August 25, 2025 07:39
@PijukatelPijukatel
synchronize #552
unique-key
Status Cancelled
Total duration 1m 5s
Artifacts

run_code_checks.yaml

on: pull_request
Integration tests  /  Approve integration tests for PRs from forks
34s
Integration tests / Approve integration tests for PRs from forks
Docs check  /  Docs check
1m 2s
Docs check / Docs check
Matrix: Integration tests / Integration tests
Matrix: Lint check / Lint check
Matrix: Type check / Type check
Matrix: Unit tests / Unit tests
Matrix: Integration tests / Integration tests for PRs from forks
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 notices
Run code checks
Canceling since a higher priority waiting request for integration_tests exists
Unit tests / Unit tests (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Unit tests / Unit tests (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Unit tests / Unit tests (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Unit tests / Unit tests (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677