terminal: keystrokes typed into a brand-new split window are sometimes lost (~1 in 16) #420

New issue

Open

opened 2026-11-07 08:50:29 +00:00 by kayg · 0 comments

kayg commented

2026-11-07 08:50:29 +00:00

Owner

Observed by J305 during #395's real-server work (06c53cb40 release binary, compute01): in about 1 of 16 attempts, keystrokes typed into a brand-new split window right after it appeared never reached the shell.

Not yet triaged. Possible causes: input sent before the terminal session is attached, or a focus race on the new window. Repro idea: split, then type at once in a loop of 30; count lost inputs. Related: #411 (rapid split refusals) and #395.

Observed by J305 during #395's real-server work (06c53cb40 release binary, compute01): in about 1 of 16 attempts, keystrokes typed into a brand-new split window right after it appeared never reached the shell. Not yet triaged. Possible causes: input sent before the terminal session is attached, or a focus race on the new window. Repro idea: split, then type at once in a loop of 30; count lost inputs. Related: #411 (rapid split refusals) and #395.

No labels

launch-qa

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kayg/infraternal#420

No description provided.

Rows
Columns