fix(node): Guard against invalid maxSpanWaitDuration values

[mydea]

Today, if you pass e.g. Infinity or another large number to maxSpanWaitDuration, the SDK will error out because we try to do new Array(maxSpanWaitDuration), which is impossible.

Ideally, we can properly allow an infinite wait time, but for now this adds checks to ensure only valid values are passed in there, and we do not explode.

See #14154 (comment)

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	23.27 KB	-	-
@sentry/browser - with treeshaking flags	21.94 KB	-	-
@sentry/browser (incl. Tracing)	35.75 KB	-	-
@sentry/browser (incl. Tracing, Replay)	72.98 KB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.38 KB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	77.29 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	89.78 KB	-	-
@sentry/browser (incl. Feedback)	40.02 KB	-	-
@sentry/browser (incl. sendFeedback)	27.88 KB	-	-
@sentry/browser (incl. FeedbackAsync)	32.67 KB	-	-
@sentry/react	25.94 KB	-	-
@sentry/react (incl. Tracing)	38.58 KB	-	-
@sentry/vue	27.47 KB	-	-
@sentry/vue (incl. Tracing)	37.59 KB	-	-
@sentry/svelte	23.43 KB	-	-
CDN Bundle	24.41 KB	-	-
CDN Bundle (incl. Tracing)	37.4 KB	-	-
CDN Bundle (incl. Tracing, Replay)	72.6 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	77.96 KB	-	-
CDN Bundle - uncompressed	71.69 KB	-	-
CDN Bundle (incl. Tracing) - uncompressed	110.97 KB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	225.04 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	238.26 KB	-	-
@sentry/nextjs (client)	38.86 KB	-	-
@sentry/sveltekit (client)	36.26 KB	-	-
@sentry/node	162.34 KB	+0.07%	+116 B 🔺
@sentry/node - without tracing	98.53 KB	+0.11%	+110 B 🔺
@sentry/aws-serverless	126.23 KB	+0.1%	+125 B 🔺

View base workflow run