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
{{ message }}
Repository navigation
Commit ea6b1f3
Browse filesBrowse the repository at this point in the historyBrowse files
fix: guard the active runner environment behind accessors (#79) (#80)
Service.ActiveEnv was an exported interface field written by a
specialization's Init/Stop and read by the Code, Tooling and REPL
handlers on their own gRPC goroutines, with nothing ordering the two.
A specialization cannot close that gap: its lifecycle lock is not
reachable from these handlers.
The field is now unexported behind ActiveEnv/SetActiveEnv under an
RWMutex, and fixPython snapshots it once per request so a publish or
clear landing mid-fix cannot send ruff check and ruff format to two
different interpreters.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments