getsentry / getsentry/sentry-javascript
[Flaky CI]: E2E nextjs-16-cf-workers Test - tests/streaming-rsc-error.test.ts › Should capture errors for crashing streaming promises in server components when `Sentry.captureRequestError` is added to the `onRequestError` hook
- Vorherrschende Sprache
- TypeScript
- Sterne
- 8.7k
- Forks
- 1.8k
- Ø Merge
- 1 T. 17 Std.
- Gemergte PRs (30 T.)
- 515
Beschreibung
### Flakiness Type
Other / Unknown
### Name of Job
E2E nextjs-16-cf-workers Test
### Name of Test
[chromium] › tests/streaming-rsc-error.test.ts:4:5 › Should capture errors for crashing streaming promises in server components when `Sentry.captureRequestError` is added to the `onRequestError` hook
### Link to Test Run
https://github.com/getsentry/sentry-javascript/actions/runs/33626904429/job/100237921295
---
_This issue was automatically created._
Beitragsleitfaden
Rechercherichtung
Start by running the named E2E nextjs-16-cf-workers job and reading tests/streaming-rsc-error.test.ts, especially the test at line 4. Use the linked workflow run to identify why the test is intermittent, then verify the test passes reliably without losing coverage for crashing streaming promises and Sentry.captureRequestError in the onRequestError hook.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- nextjs, typescript
- Bereich
- ci-cd, testing-qa
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 52/100