Decrement requests_active only after the response body is closed.
#507
Annotations
39 errors and 15 warnings
|
3.3 on macos gems/rack-v3.rb
Process completed with exit code 1.
|
|
4.0 on ubuntu gems/rack-v1.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on macos gems/rack-v2.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on macos gems/rack-head.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on macos gems/rack-head.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on macos gems/rack-v3.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on macos gems/rack-v1.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on macos gems/rack-v1.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on macos gems/rack-v2.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on macos gems/rack-v1.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
head on ubuntu
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on ubuntu gems/rack-head.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on ubuntu gems/rack-head.rb
The operation was canceled.
|
|
3.4 on ubuntu gems/rack-v3.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on ubuntu gems/rack-v3.rb
The operation was canceled.
|
|
3.4 on ubuntu gems/rack-head.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on ubuntu gems/rack-head.rb
The operation was canceled.
|
|
3.3 on ubuntu gems/rack-v3.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on ubuntu gems/rack-v3.rb
Process completed with exit code 1.
|
|
4.0 on ubuntu gems/rack-v3.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on ubuntu gems/rack-v3.rb
The operation was canceled.
|
|
3.3 on ubuntu gems/rack-v1.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on ubuntu gems/rack-v1.rb
The operation was canceled.
|
|
3.3 on ubuntu gems/rack-v2.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on ubuntu gems/rack-v2.rb
The operation was canceled.
|
|
3.4 on ubuntu gems/rack-v2.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on ubuntu gems/rack-v2.rb
The operation was canceled.
|
|
4.0 on ubuntu gems/rack-head.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on ubuntu gems/rack-head.rb
The operation was canceled.
|
|
3.3 on macos gems/rack-head.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.3 on macos gems/rack-head.rb
The operation was canceled.
|
|
4.0 on ubuntu gems/rack-v2.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on ubuntu gems/rack-v1.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on ubuntu gems/rack-v2.rb
The operation was canceled.
|
|
3.4 on ubuntu gems/rack-v1.rb
The operation was canceled.
|
|
3.4 on macos gems/rack-v2.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
3.4 on macos gems/rack-v2.rb
The operation was canceled.
|
|
4.0 on macos gems/rack-v3.rb
The strategy configuration was canceled because "test.macos_3_3_gems_rack-v3_rb" failed
|
|
4.0 on macos gems/rack-v3.rb
The operation was canceled.
|
|
3.3 on macos gems/rack-v3.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.3 on ubuntu gems/rack-head.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.4 on ubuntu gems/rack-v3.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.4 on ubuntu gems/rack-head.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.3 on ubuntu gems/rack-v3.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
4.0 on ubuntu gems/rack-v3.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.3 on ubuntu gems/rack-v1.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.3 on ubuntu gems/rack-v2.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.4 on ubuntu gems/rack-v2.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
4.0 on ubuntu gems/rack-head.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.3 on macos gems/rack-head.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
4.0 on ubuntu gems/rack-v2.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.4 on ubuntu gems/rack-v1.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
3.4 on macos gems/rack-v2.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
4.0 on macos gems/rack-v3.rb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|