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
Review-traced, unreproduced findings from the issue batch (settings race, keybinding save, idle text, last-checked time) #394
Findings that code review traced during pull request 387 and that no test, lab run or Profiler record reproduced. They were not changed in that pull request. For the first three a fix was written and withdrawn, because a check of the fix found it would break behaviour that works today.
Saved session defaults, two windows. Two windows that save providerSessionDefaults at the same instant can overwrite each other in one ordering. Withdrawn fix: a server-side cleanup under the settings lock; it could overwrite a model chosen in the same request, turn an invalid map into a valid one that drops other providers, and leave a retired default saved against an older server.
Keybindings after a failed save. A failed keybinding save can leave the rejected binding visible to a new config subscriber. Withdrawn fix: committing the rules only after the file write; a disconnect between the rename and the commit could erase a saved binding.
Text of an answer with no turn while a new message is being sent. A message sent while Claude streams an answer with no turn open can leave that answer's text marked streaming. Withdrawn fix: completing the text on the early result; it sent a context query to Claude during the new message's turn.
Config stream, "last checked" after a resync. After a resync, a manual refresh that changes only timestamps can be suppressed while the held version advances, leaving the Settings "last checked" time stale. An attempted fix broke an existing test of the same stream.
Closing as not planned: none of the four was reproduced by a test or a run, and three attempted fixes introduced regressions that their own checks caught. Each needs a failing test first; reopen the specific item with one.
Activity
mubeda commentedon Nov 19, 2026
Closing as not planned: none of the four was reproduced by a test or a run, and three attempted fixes introduced regressions that their own checks caught. Each needs a failing test first; reopen the specific item with one.