Let legacy ws clients know about invalid data frames #11229
Triggered via pull request
September 17, 2024 19:59
Status
Cancelled
Total duration
1m 52s
Artifacts
–
test.yml
on: pull_request
💻 Generate test matrix
10s
Matrix: unit-tests
🆙 Upload Coverage
0s
Annotations
160 errors and 55 warnings
🔬 Tests on 3.10 (gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.10 (gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.11 (gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.12 (gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Starlette tests on 3.11 (starlette=0.27.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.11 (gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Starlette tests on 3.11 (starlette=0.28.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.12 (gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.13 (gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Starlette tests on 3.11 (starlette=0.27.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Starlette tests on 3.11 (starlette=0.26.1, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Starlette tests on 3.11 (starlette=0.26.1, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.8 (gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.13 (gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.9 (gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.8 (gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Starlette tests on 3.11 (starlette=0.28.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Tests on 3.9 (gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=channels, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=aiohttp, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=chalice, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=fastapi, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=chalice, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=fastapi, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=aiohttp, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=channels, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=flask, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.9 (pydantic=2.9.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.9 (pydantic=1.10, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.9 (pydantic=2.9.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=sanic, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=quart, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=flask, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=quart, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=litestar, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Type checkers tests on 3.11
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=litestar, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Test integrations on 3.11 (integration=sanic, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Type checkers tests on 3.12
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Type checkers tests on 3.10
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Type checkers tests on 3.8
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Type checkers tests on 3.13
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Type checkers tests on 3.9
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=2.8.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=2.8.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=4.0.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=4.0.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=3.2.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=3.2.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=4.0.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=4.0.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.12 (pydantic=1.10, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.12 (pydantic=1.10, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.11 (pydantic=1.10, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=1.10, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.8 (pydantic=2.8.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.8 (pydantic=2.8.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.13 (pydantic=1.10, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.13 (pydantic=1.10, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=4.2.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=4.2.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=4.0.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=4.0.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=4.1.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=4.1.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=4.2.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=4.2.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.8 (pydantic=1.10, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.8 (pydantic=1.10, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.10 (pydantic=1.10, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.10 (pydantic=1.10, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.10 (pydantic=2.8.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.12 (pydantic=2.8.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.10 (pydantic=2.8.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.12 (pydantic=2.8.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 CLI tests on 3.12
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 CLI tests on 3.12
The operation was canceled.
|
🔬 Pydantic tests on 3.12 (pydantic=2.9.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.9 (pydantic=2.8.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.12 (pydantic=2.9.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.9 (pydantic=2.8.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=4.2.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.10 (pydantic=1.10, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=4.2.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.10 (pydantic=1.10, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.13 (pydantic=2.9.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.13 (pydantic=2.9.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=4.1.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=4.1.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=3.2.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=3.2.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=4.1.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=4.1.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=3.2.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=3.2.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=4.2.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=4.2.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.8 (pydantic=2.9.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.8 (pydantic=2.9.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=3.2.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=3.2.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.13 (pydantic=1.10, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.13 (pydantic=1.10, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.10 (pydantic=2.8.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.10 (pydantic=2.8.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.12 (pydantic=2.8.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.12 (pydantic=2.8.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.12 (pydantic=2.9.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.12 (pydantic=2.9.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 CLI tests on 3.9
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 CLI tests on 3.9
The operation was canceled.
|
🔬 CLI tests on 3.13
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=1.10, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 CLI tests on 3.13
The operation was canceled.
|
🔬 Pydantic tests on 3.11 (pydantic=1.10, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.10 (pydantic=2.9.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.10 (pydantic=2.9.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.12 (pydantic=1.10, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.12 (pydantic=1.10, gql_core=3.2.3)
The operation was canceled.
|
🔬 Django tests on 3.12 (django=4.0.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.12 (django=4.0.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.13 (pydantic=2.8.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.13 (pydantic=2.8.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.11 (pydantic=2.8.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=2.8.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.11 (pydantic=2.9.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=2.9.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.9 (pydantic=1.10, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.9 (pydantic=1.10, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.10 (pydantic=2.9.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.10 (pydantic=2.9.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Django tests on 3.11 (django=4.1.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Django tests on 3.11 (django=4.1.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.13 (pydantic=2.9.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.13 (pydantic=2.9.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.8 (pydantic=1.10, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.8 (pydantic=1.10, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.8 (pydantic=2.8.0, gql_core=3.3.0a6)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.8 (pydantic=2.8.0, gql_core=3.3.0a6)
The operation was canceled.
|
🔬 Pydantic tests on 3.8 (pydantic=2.9.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.8 (pydantic=2.9.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.11 (pydantic=2.9.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.11 (pydantic=2.9.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 Pydantic tests on 3.13 (pydantic=2.8.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.13 (pydantic=2.8.0, gql_core=3.2.3)
The operation was canceled.
|
🪟 Tests on Windows
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🪟 Tests on Windows
Process completed with exit code 1.
|
🪟 Tests on Windows
Codecov:
Failed to properly upload report: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
|
🪟 Tests on Windows
The operation was canceled.
|
🔬 Pydantic tests on 3.9 (pydantic=2.8.0, gql_core=3.2.3)
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 Pydantic tests on 3.9 (pydantic=2.8.0, gql_core=3.2.3)
The operation was canceled.
|
🔬 CLI tests on 3.10
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 CLI tests on 3.10
The operation was canceled.
|
🔬 CLI tests on 3.11
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 CLI tests on 3.11
The operation was canceled.
|
🔬 CLI tests on 3.8
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
🔬 CLI tests on 3.8
The operation was canceled.
|
📈 Benchmarks
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
✨ Lint
Canceling since a higher priority waiting request for 'inform-clients-about-invalid-data-frames' exists
|
✨ Lint
The operation was canceled.
|
🔬 Pydantic tests on 3.11 (pydantic=2.8.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=4.0.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=3.2.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=4.0.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.12 (pydantic=1.10, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.11 (pydantic=1.10, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.8 (pydantic=2.8.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.13 (pydantic=1.10, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=4.2.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=4.0.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=4.1.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=4.2.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.8 (pydantic=1.10, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.10 (pydantic=1.10, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.10 (pydantic=2.8.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.12 (pydantic=2.8.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 CLI tests on 3.12
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.12 (pydantic=2.9.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.9 (pydantic=2.8.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=4.2.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.10 (pydantic=1.10, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.13 (pydantic=2.9.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=4.1.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=3.2.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=4.1.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=3.2.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=4.2.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.8 (pydantic=2.9.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=3.2.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.13 (pydantic=1.10, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.10 (pydantic=2.8.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.12 (pydantic=2.8.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.12 (pydantic=2.9.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 CLI tests on 3.9
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 CLI tests on 3.13
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.11 (pydantic=1.10, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.10 (pydantic=2.9.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.12 (pydantic=1.10, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.12 (django=4.0.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.13 (pydantic=2.8.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.11 (pydantic=2.8.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.11 (pydantic=2.9.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.9 (pydantic=1.10, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.10 (pydantic=2.9.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Django tests on 3.11 (django=4.1.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.13 (pydantic=2.9.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.8 (pydantic=1.10, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.8 (pydantic=2.8.0, gql_core=3.3.0a6)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.8 (pydantic=2.9.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.11 (pydantic=2.9.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.13 (pydantic=2.8.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 Pydantic tests on 3.9 (pydantic=2.8.0, gql_core=3.2.3)
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 CLI tests on 3.10
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 CLI tests on 3.11
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|
🔬 CLI tests on 3.8
No files were found with the provided path: coverage.xml. No artifacts will be uploaded.
|