Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Port cloudflare-integration-tests to span streaming

Abierto
#24,132 1 comentario 0 reacciones 1 asignado Ver en GitHub

@JPeer264 ya está trabajando en esto.

Desde el 7/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

javascript Task

Port dev-packages/cloudflare-integration-tests to span streaming. Span streaming is the default, so every suite that still pins traceLifecycle: 'static' covers behaviour we no longer ship.

Part of SDK-1425, one tracking issue per integration test package.

Scope

  • 102 traceLifecycle: 'static' pins across 82 files
  • 2 suites already have a -streamed twin: tracing/ignoreSpans-streamed and public-api/startSpan-streamed
  • tracing/d1 uses an env-gated STREAMED switch
  • This package has no shared span helpers. Every streamed test hand-rolls its own getSpanContainer, so the helper work comes first.

How to port a suite

  1. Remove the traceLifecycle: 'static' pin from every Sentry.init in the suite.
  2. If a -streamed twin exists, fold it back: delete the static original and rename the twin to the base name.
  3. Rewrite the assertions from transaction envelopes to span v2 against the shared helper added in the first sub-issue:
    • event.transaction becomes span.name
    • contexts.trace.op becomes the sentry.op attribute plus span.is_segment
    • contexts.trace.data['x'] becomes span.attributes['x'], which has the shape { value, type }
    • transaction_info.source becomes the sentry.segment.name.source attribute

Watch for span names that become low cardinality under streaming: http.server, http.client, db, cache and gen_ai.

Reference suite: suites/public-api/startSpan-streamed.

Keep static trace lifecycle coverage

Keep one suite on the static pin as a guard rather than duplicating each one. Name it in the PR.

Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
1.9k
Merge medio
1 d 18 h
PR fusionados (30 d)
562

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de getsentry/sentry-javascript

Todos los issues de getsentry/sentry-javascript

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.