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
We’ve been testing the new feature flag functionality (currently in beta) and ran into an issue that appears to have been addressed by #4034
The fix introduces a lock to prevent concurrency issues, but we were wondering why FlagBuffered is shared across contexts rather than being thread-local. Wouldn’t it make more sense for it to be per-context to avoid the need for locking?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Sentry team,
We’ve been testing the new feature flag functionality (currently in beta) and ran into an issue that appears to have been addressed by #4034
The fix introduces a lock to prevent concurrency issues, but we were wondering why
FlagBufferedis shared across contexts rather than being thread-local. Wouldn’t it make more sense for it to be per-context to avoid the need for locking?Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions