Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Port cloudflare-integration-tests to span streaming

Aperta
#24,132 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

@JPeer264 ci sta già lavorando.

Dal 7/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.

Lingua principale
TypeScript
Stelle
8.7k
Fork
1.9k
Merge medio
1g 18h
PR unite (30g)
562

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/sentry-javascript

Tutte le issue di getsentry/sentry-javascript

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.