mirror of
https://github.com/openai/codex.git
synced 2026-11-22 15:15:18 +00:00
Avoid paginated resume requests for verified legacy rollouts (#38604)
## Why Resuming a known legacy rollout with `excludeTurns` first requires the TUI to retry after the app server rejects paginated history loading. ## What changed - Carry the history mode reported by the session picker into the resume flow. - For embedded app-server sessions, resume a legacy rollout with its turns when the rollout is still legacy and background migration cannot race the check. - Keep requesting paginated history when the picker metadata may be stale, migration is enabled or active, or the app server is remote. ## Testing Added coverage for picker server replacement, background migration, maintenance lock contention, stale history metadata, and paginated resume requests. GitOrigin-RevId: 2300d1ad93a817eeeeb8f8ed60b073400ddf7106
This commit is contained in:
1 parent
588ee89324
commit
1bb6384c19
13 files changed
+455
-90
No files matched your search
@@ -502,6 +502,7 @@ mod tests {
|
||||
&SessionTarget {
|
||||
path: Some(rollout_path.clone()),
|
||||
thread_id,
|
||||
history_mode: None,
|
||||
},
|
||||
CwdPromptAction::Fork,
|
||||
ResumeCwdContext {
|
||||
@@ -535,6 +536,7 @@ mod tests {
|
||||
&SessionTarget {
|
||||
path: None,
|
||||
thread_id: ThreadId::new(),
|
||||
history_mode: None,
|
||||
},
|
||||
CwdPromptAction::Resume,
|
||||
ResumeCwdContext {
|
||||
|
||||
Reference in new issue
Block a user