App Router: OTel spans during cache component fallback resume reuse the trace id

(0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)TypeScript (384 Forks)github user discovery

adapter-api-e2ehelp wanted

Repository-Metriken

Stars: (8.625 Sterne)
PR-Merge-Metriken: (Durchschn. Merge 1T 1h) (462 gemergte PRs in 30 T)

Beschreibung

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.2.6, 2026-05-22).

Problem

Spans created during fallback resume inside a Cache Component should have a fresh trace id distinct from the build-time render. vinext reuses the same trace id (e.g. 11989306), implying the span context is not being re-created per request resume.

Trace id reused across build-time render and runtime resume

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

test/e2e/app-dir/cache-components-allow-otel-spans/cache-components-allow-otel-spans.test.ts

Recommendation

Reproduce first in vinext's own test suite. Use the existing cache-components-allow-otel-spans fixture and assert the trace id changes between build-time prerender and runtime resume.
Reset the OTel context on resume. Each cache-component resume should start a new span/trace context, not inherit the prerender's.

Contributor Guide

Research-Richtung: Prüfe das Test Fixture cache components allow otel spans, reproduziere das Problem, um zu bestätigen, dass die Trace ID wiederverwendet wird, und setze dann den OTel Span Kontext beim Fortsetzen einer Cache Komponente zurück, um eine neue Trace ID pro Anfrage zu gewährleisten.
Tech Stack: typescriptjavascriptnodejs
Domain: backenddeveloper experience
Issue Type: Fehler
Schwierigkeit: 2
Geschätzte Zeit: Halber Tag
Aktivitätsstatus: Frisch
Klarheit: Klar
Voraussetzungen: GitNode.jsTypeScript
Einsteigerfreundlichkeit: 70