Reproduction for sentry-javascript#17742

[nicohrubec]

Summary

Reproduces sentry-javascript#17742 — breadcrumbs from NestJS background jobs leak into HTTP request error events.

Background jobs run outside the HTTP request context, so they add breadcrumbs to the default isolation scope. When a new HTTP request arrives, httpServerIntegration clones the default scope via getIsolationScope().clone() — inheriting all stale breadcrumbs from background jobs.

Background Job Frameworks Covered

Framework	Decorator	External Dep	Env Var	Leak Confirmed
@nestjs/schedule	@Interval	None	Always active	Yes
@nestjs/event-emitter	@OnEvent	None	Always active	Yes
@nestjs/bullmq	@Processor	Redis	REDIS_URL	Yes
nestjs-graphile-worker	@Task	PostgreSQL	DATABASE_URL	Yes

Root Cause

In packages/node-core/src/integrations/http/httpServerIntegration.ts:185:

const isolationScope = getIsolationScope().clone();

This clones the default isolation scope, which has been polluted by background job breadcrumbs.

How to Run

cd sentry-javascript/17742
cp .env.example .env  # then add your SENTRY_DSN
npm install
npm run test:repro

Optionally set REDIS_URL=redis://localhost:6379 and/or DATABASE_URL=postgres://user:pass@localhost:5432/dbname to also test BullMQ and Graphile Worker leaking.

Expected Output

=== Sentry Event Breadcrumbs (1 total) ===
  [0] category=http-request, message=About to trigger an error in HTTP handler

  No leaked breadcrumbs detected (isolation working).

Actual Output (all 4 frameworks enabled)

*** BUG CONFIRMED: Breadcrumbs leaked from background jobs! ***
  Leaked: schedule-job: 5, event-job: 4, bullmq-job: 3, graphile-job: 2

Setup Details

• Follows official Sentry NestJS docs — uses SentryModule.forRoot(), SentryGlobalFilter as APP_FILTER
• Errors are thrown naturally (no manual captureException)
• BullMQ and Graphile Worker are conditionally loaded based on env vars

🤖 Generated with Claude Code

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

BullMQ connection silently ignores invalid url property

Medium Severity

The BullModule.forRoot({ connection: { url: process.env.REDIS_URL } }) call passes a url property in the connection options, but ioredis's RedisOptions does not support a url property (the feature request was explicitly rejected in ioredis#871). The url field is silently ignored, and ioredis defaults to localhost:6379. This means the BullMQ test case only works by coincidence when Redis happens to be on localhost, and will silently connect to the wrong server for any other REDIS_URL value. The connection URL needs to be parsed into host/port/password fields or an ioredis instance created from the URL string.