Skip to content

feat(fastapi): Capture request body on segment span under streaming #7767

feat(fastapi): Capture request body on segment span under streaming

feat(fastapi): Capture request body on segment span under streaming #7767

Triggered via pull request April 27, 2026 18:23
Status Cancelled
Total duration 4m 38s
Artifacts 14

test-integrations-flags.yml

on: pull_request
Matrix: Flags
All Flags tests passed
3s
All Flags tests passed
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 14 warnings
Flags (3.13, ubuntu-22.04)
Canceling since a higher priority waiting request for Test Flags-py-2322-port-event-processor-data-to-span-first-rme79 exists
Flags (3.13, ubuntu-22.04)
The operation was canceled.
All Flags tests passed
Process completed with exit code 1.
Test Flags
Canceling since a higher priority waiting request for Test Flags-py-2322-port-event-processor-data-to-span-first-rme79 exists
Flags (3.10, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.10, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%
Flags (3.9, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.9, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%
Flags (3.7, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.7, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%
Flags (3.8, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.8, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%
Flags (3.12, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.12, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%
Flags (3.14t, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.14t, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%
Flags (3.14, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
Flags (3.14, ubuntu-22.04)
❌ Patch coverage check failed: 8.33% < target 80%

Artifacts

Produced during runtime
Name Size Digest
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
116 KB
sha256:3cfffcd1f5e7fa381f2faeadc0ecd86555a8f2721a158556e1f6c4f6adefa307
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
115 KB
sha256:d01fce2a849e30eebdff43c90eea5ae7789aeeda82a3e7704e58b1cbedf44bb7
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
115 KB
sha256:4a15aff0465fc06755fbfe98437e2fc39c6143a6b72ef1947b8bc77ff13cfc94
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
115 KB
sha256:c903f5aed106394b2cd47d44cb677b55319e4f15646602ffd9de5abb23e37f89
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
116 KB
sha256:3b20fd5fbd35a267f10e4ddd398a594fb39a38351a1a74cb5f18db3cd0530c09
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
116 KB
sha256:1e96c2e0d1131cb6295b8554dca0f975398c3b30669c21a64f18d593d92b3080
codecov-coverage-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
116 KB
sha256:870273e0766c7a6b78c663834481da4be91ebee23f081fd5ae34752911941c52
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
229 Bytes
sha256:008fbeed9a45bfca3ca6b7bc9ef75ca0b1f0af39111ad6e36ac6ba8c5769c1de
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
230 Bytes
sha256:38e5d47a102b73bd692d5345cae6b031e900ac81949f6321145b2990a15ee225
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
230 Bytes
sha256:8de2931a51d3ea5bbbb32fdfd3bb5f5c8a10b33f3f2b975387855da30730279f
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
230 Bytes
sha256:26b55ce8fabaf22316da8a708cd27c68d77929dbcb0f7a3bf351c0f8be4c7fc6
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
231 Bytes
sha256:8c87eaf709402bcde113c6c4db14dfe29b5a2bf5924b75b3427a922ebf90c6c1
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
230 Bytes
sha256:174227b6ff992bcabf146a6944ecaaf540b8b121891058f838c2165fa814c986
codecov-test-results-py-2322-port-event-processor-data-to-span-first-rme79-test-flags
231 Bytes
sha256:4c14be177ab41e1e96d244c471d3bbe8fc55c9fed025cecb9c9bbcfd0983d183