Table view stuck leave antares on secondary virtual desktop for long time

[D-nov]

Steps to reproduce (unknown reproducibility):

• open ssh connection (or more)
• open few tables
• leave antares on secondary virtual desktop for long time
• disconnect the connection using the button

Actual result:

• connection is closed, but the view with the tables data stay open and unresponsive
• issue is resolved after restarting the app

Aditional info: ubuntu, mariadb, antares v0.5.12 or up

[D-nov]

Update: it's turns out it's pretty consistent.

I think the ssh connection is lost or closed after some time of not using the app.

Actual result: no indication that the ssh connection is closed or lost and the app keeps showing as connect and all tables stay open, but it's unusable. You have to relaunch the tool and reconnect to use it again.

Expected result: keep the connection alive for as long as the tool is open.

PS: @Fabio286 I didn't mean to close the issue, sorry. :)
I do not know what I clicked to close it.

[Fabio286]

Hi Danny,

thank you for this additional information.

I ran some tests but could not replicate the error conditions.
At this point I think I will first implement a system that closes the connection when an error happens in the SSH connection.
Second, I will evaluate the implementation of a keep alive after being able to replicate the error conditions.

Issue reopened 😉.

[D-nov]

I'm still learning, so I use a preconfigured env and can't share specific setup information, but if it helps I think the ssh is configured to close after a set time of inactivity.

[Fabio286]

I've implemented a keepalive and from my tests this solve the problem.
Let me know if from next release you still face this issue.

[D-nov]

Thanks for the Christmas surprise, but sadly it doesn't seem to be solved. 😞
I opened SSH session, left it in the background (as already described in the issue) (also locked the gnome desktop if it helps) and when I needed the DB again (around 1h later) Antares was dead already and I had to relaunch it.

[Fabio286]

The fix I was telling you about is in the upcoming version (0.7.2).
I am keeping this issue open and waiting for your confirmation to close it.

[D-nov]

I do not have a foolproof way of reproducing this, but so far it hasn't occurred.
I'll keep watch over the next few days, but (since it used to happen almost daily) I can assume you solved it this time 🥳