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
fix(Session.attach): Remove refresh() call that fails after session killed
When a user attaches to a tmux session via `tmuxp load`, works in the
session, then kills it (e.g., closes all windows) before detaching,
the Session.attach() method would raise TmuxObjectDoesNotExist.
This happened because attach() called self.refresh() after the
attach-session command returned. Since attach-session is a blocking
interactive command, the session state can change arbitrarily during
attachment - including being killed entirely.
The refresh() call was semantically incorrect for interactive commands:
- attach-session blocks until user detaches
- Session state can change during attachment
- Refreshing after such a command makes no sense
Introduced in: 9a5147a (feat(Session.attach): Add Session.attach())
Triggered by: tmuxp fdafdd2b switching from attach_session() to attach()
Adds regression test using NamedTuple + parametrize + test_id pattern.
0 commit comments