sshnp (pure dart): "user" ssh session doesn't close properly if the "tunnel" session closes

[XavierChanth]

Describe the bug

• When using the desktop app, if a shell is open and we lose internet, then the session locks, since the dartssh2 user session doesn't know that the tunnel transport has closed.

Steps to reproduce

1. Start desktop app session
2. Turn off internet

Related branch: fix/locked-up-session

Expected behavior

Some callback / future that allows detection of the tunnel session closing from the SshnpRemoteProcess object.

Screenshots

No response

Smartphones

N/A

Were you using an atApplication when the bug was found?

No response

Additional context

No response

[XavierChanth]

In addition, in noports core, initialization doesn't do any Future.catchError() calls to handle async errors properly

[XavierChanth]

We have wrapped the pure-dart session call in a runZonedGuarded clause for the desktop application. This bug is low priority, since we were able to handle it gracefully. The CLI application already handles this since we already do the runZonedGuarded call for it.

[XavierChanth]

At this point, I would consider this a low priority bug, since there is a valid, reliable workaround.