Skip to content

Conversation

easong-openai
Copy link
Collaborator

We need to at least tell the user when we got an error. I've never seen it actually recover from the background stream error, so IMO the next step is probably to just cancel the turn until we fix that. Will do it as a second PR if people agree.

Comment on lines +284 to +287
} => {
let env = std::env::var("MANUALLY_DEBUG_TUI_BACKGROUND_RETRY")
.unwrap_or_default();
if env == "1" {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
} => {
let env = std::env::var("MANUALLY_DEBUG_TUI_BACKGROUND_RETRY")
.unwrap_or_default();
if env == "1" {
} if std::env::var("MANUALLY_DEBUG_TUI_BACKGROUND_RETRY").is_ok_and(|v| v == "1") => {
// ...

then you don't have to repeat the dispatch_key_event logic.

Comment on lines 643 to 650
let lines: Vec<Line<'static>> = vec![
Line::from(vec![
"ℹ".magenta(),
" ".into(),
Span::styled(message, Style::default().add_modifier(Modifier::DIM)),
]),
Line::from(""),
];
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i believe we removed these because we emit these whenever there's an otherwise unhandled event, which looks weird when these get added for other features that the tui doesn't handle yet. PatchApplyEnd used to be one of these though i'm not sure it still is.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants