chore: remove steal fallback from debuggableNavigatorLock#43172
chore: remove steal fallback from debuggableNavigatorLock#43172
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Central YAML (base), Repository UI (inherited), Organization UI (inherited) Review profile: CHILL Plan: Pro Cache: Disabled due to Reviews > Disable Cache setting Disabled knowledge base sources:
📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe pull request modifies the Navigator Locks timeout handling in Comment |
Braintrust eval report
|
The SDK now handles orphaned lock recovery via steal internally (supabase-js#2106). Keep the BroadcastChannel observability wrapper for Sentry signals. The steal-based orphaned lock recovery in
debuggableNavigatorLock(packages/common/gotrue.ts) (introduced in #39868) is now redundant, supabase-js#2106 handles this natively in the SDK.Removes the
navigator.locks.request({ steal: true })block while keeping the BroadcastChannel wrapper that sends lock-holder stack traces to Sentry.Related: supabase/supabase-js#2106, supabase/supabase-js#2125