Hi @userxfce,
Thanks for all the bug reports! This one is really interesting - and I saw it once when I ran 'cargo uninstall' and then 'brew install'. I think what happened here is the v0.3.7 tab binary was removed. The daemon re-launches it's own executable to spawn PTY processes, and if the tab binary is removed it can't do this.

Removing the ~/.tab directory was what fixed it - because it removed the daemon pidfile. You can also use tab --shutdown after installing a new version to trigger a complete shutdown of the daemon and all PTY processes.

I think there are a few things that can be improved here:

Add documentation that tab --shutdown is recommended after upgrades.
Print a warning if the daemon binary and the command-line binary are not the same, and suggest tab --shutdown.
Print a stronger warning (or refuse to connect) if there are breaking API changes between the command-line and daemon binaries.

I also have an item on the backlog (#44) to shut down the daemon when the tab binary changes, but I've been holding off on implementing it because I'm worried about conflicting installations (e.g. both cargo and homebrew) causing weird behavior with daemon shutdowns.

Removing the tab binary after an upgrade breaks the running tab daemon #163

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions