Persistent child ssh process blocks refresh

[Julian Edwards]

I have my ssh config set up to use ControlMaster to reduce back and forth socket establishment comms over a high-latency endpoint.

When using the VSCode snap ("code") and it needs a refresh, I can terminate the code application, but doing a 'snap refresh' still thinks it's running because of the child SSH process (which was started when I did a Github push):

± sudo snap refresh code
error: cannot refresh "code": snap "code" has running apps (code), pids: 1587331
± ps -fe|grep 1587331
juledwar 1587331 1 0 08:12 ? 00:00:11 ssh: /home/juledwar/.ssh/sockets/git@<redacted>-22 [mux]

Killing the persistent SSH process allows the refresh to go ahead. This should not be necessary, it's not part of the snap's processes.

[Julian Edwards (julian-edwards)]

Besides this annoying refresh behaviour, beforehand the snap would be refreshed even when the VScode application is running, and prompt me to restart. This all happened behind the scenes, and restarting took 2 seconds.

The new process is just an awful UX.