refactor: replace ensure_future with create_task in ASGI #884
joamagmain.yml
on: push
Matrix: Build macOS
Matrix: Build PyPy
Matrix: Build Windows
Matrix: Build
Annotations
104 errors and 16 warnings
|
Build (3.5, tiny)
Process completed with exit code 1.
|
|
Build (3.9, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.12, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.11, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.14, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.14, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.6, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.6, tiny)
Process completed with exit code 1.
|
|
Build (2.7, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (2.7, tiny)
The operation was canceled.
|
|
Build (3.10, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.7, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.7, mongo:6)
The operation was canceled.
|
|
Build (3.6, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.6, mongo:6)
The operation was canceled.
|
|
Build (3.8, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.8, mongo:8)
The operation was canceled.
|
|
Build (3.12, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.12, mongo:6)
The operation was canceled.
|
|
Build (3.6, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.6, mongo:8)
The operation was canceled.
|
|
Build (3.10, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.10, mongo:8)
The operation was canceled.
|
|
Build (3.6, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.6, mongo:7)
The operation was canceled.
|
|
Build (3.9, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.9, mongo:7)
The operation was canceled.
|
|
Build (3.7, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.7, tiny)
The operation was canceled.
|
|
Build (3.8, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.8, tiny)
The operation was canceled.
|
|
Build (3.12, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.12, mongo:8)
The operation was canceled.
|
|
Build (3.11, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.7, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.14, tiny)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.7, mongo:7)
The operation was canceled.
|
|
Build (3.9, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.9, mongo:6)
The operation was canceled.
|
|
Build (3.11, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.11, mongo:7)
The operation was canceled.
|
|
Build (3.13, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.13, mongo:8)
The operation was canceled.
|
|
Build (3.10, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.10, mongo:6)
The operation was canceled.
|
|
Build (3.8, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.8, mongo:6)
The operation was canceled.
|
|
Build (3.10, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.10, mongo:7)
The operation was canceled.
|
|
Build (3.9, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.9, mongo:8)
The operation was canceled.
|
|
Build (3.14, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.14, mongo:6)
The operation was canceled.
|
|
Build (3.7, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.7, mongo:8)
The operation was canceled.
|
|
Build (3.13, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.13, mongo:6)
The operation was canceled.
|
|
Build (3.11, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.11, mongo:6)
The operation was canceled.
|
|
Build (3.13, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.13, mongo:7)
The operation was canceled.
|
|
Build (latest, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (latest, mongo:8)
The operation was canceled.
|
|
Build PyPy (3.6, tiny)
Process completed with exit code 1.
|
|
Build (latest, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (latest, mongo:7)
The operation was canceled.
|
|
Build (latest, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (latest, mongo:6)
The operation was canceled.
|
|
Build (3.12, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.12, mongo:7)
The operation was canceled.
|
|
Build PyPy (3.9, mongo:7)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.9, mongo:7)
The operation was canceled.
|
|
Build PyPy (3.9, mongo:6)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.9, mongo:6)
The operation was canceled.
|
|
Build PyPy (3.9, tiny)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.9, tiny)
The operation was canceled.
|
|
Build PyPy (2.7, tiny)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (2.7, tiny)
The operation was canceled.
|
|
Build PyPy (3.9, mongo:8)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.9, mongo:8)
The operation was canceled.
|
|
Build PyPy (3.10, mongo:7)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.10, mongo:7)
The operation was canceled.
|
|
Build PyPy (3.10, mongo:6)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.10, mongo:6)
The operation was canceled.
|
|
Build PyPy (3.10, tiny)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.10, tiny)
The operation was canceled.
|
|
Build (rc, mongo:8)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (rc, mongo:8)
The operation was canceled.
|
|
Build PyPy (3.10, mongo:8)
The strategy configuration was canceled because "build-pypy._3_6_tiny" failed
|
|
Build PyPy (3.10, mongo:8)
The operation was canceled.
|
|
Build (rc, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (rc, mongo:7)
The operation was canceled.
|
|
Build (rc, mongo:6)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (rc, mongo:6)
The operation was canceled.
|
|
Build (3.8, mongo:7)
The strategy configuration was canceled because "build._3_5_tiny" failed
|
|
Build (3.8, mongo:7)
The operation was canceled.
|
|
Build Windows (3.5)
Process completed with exit code 1.
|
|
Build Windows (3.7)
The strategy configuration was canceled because "build-windows._3_5" failed
|
|
Build Windows (3.6)
The strategy configuration was canceled because "build-windows._3_5" failed
|
|
Build Windows (3.6)
The operation was canceled.
|
|
Build Windows (3.9)
The strategy configuration was canceled because "build-windows._3_5" failed
|
|
Build Windows (3.9)
The operation was canceled.
|
|
Build Windows (3.14)
The strategy configuration was canceled because "build-windows._3_5" failed
|
|
Build Windows (3.14)
The operation was canceled.
|
|
Build macOS (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build macOS (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build macOS (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build macOS (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build macOS (3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build macOS (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Build Windows (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|