You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: sync HubStorage on post-init isolation_level change; stabilize specs
Two follow-ups from review:
- Configuration#isolation_level= now applies the level to HubStorage when
the SDK is already initialized, so changing Sentry.configuration.isolation_level
after Sentry.init takes effect instead of leaving the SDK on the old backend.
The default is assigned to the ivar directly in initialize so a throwaway
Configuration.new cannot clobber the active isolation level (only Sentry.init
builds the live config).
- Make the :fiber isolation_level specs deterministic across Ruby versions by
stubbing fiber_storage_available?, and add an explicit downgrade-to-:thread
spec. Previously these asserted :fiber unconditionally and would fail on the
Ruby < 3.2 CI cells, where :fiber correctly falls back to :thread.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
0 commit comments