[MariaDB / MySQL] Error: Can't add new command when connection is in closed state

[SmileYzn]

Describe the bug After a idle time, the Antares SQL give this error when execute a query in a query tab: Error: Can't add new command when connection is in closed state

That can occur in MySQL, MariaDB (That was i tested) and in different hosting providers.

Also occur the error when i disconnect and reconnect to server manually TypeError: Cannot read properties of null (reading 'includes')

To Reproduce

1. Open a new query tab
2. Execute an query
3. Wait 30~60 seconds or some more time
4. Error appears

Expected behavior The connection must be still open for new query execution

Screenshots

Screenshots attached here, click to open

Application (please complete the following information):

• App client: Antares SQL 7.25
• App version: 7.25
• Installation source: From Arch Linux AUR repository (yay -S antares-sql-bin)

Environment (please complete the following information):

• OS name: Arch Linux x86_64
• OS version: Linux 6.6.35-2-lts
• DB name: MariaDB 10.11.7 (x86_64 Linud) (At WHM/CPANEL remote host)
• DB version: 10.11.7

Additional context That can occurs in MariaDB, MySQL server from different versions and in other hosts too. Also do not matter if i use Single Connection mode or not in server connect options.

Thanks again for Antares SQL Application :pray:

[ghost]

Just stumbled upon this fun error (again), so here's some more info to it:

ENV:

• Ubuntu 24.xx
• MariaDB (also MYSQL) : mysql Ver 15.1 Distrib 10.11.8-MariaDB
• Antares SQL: current 0.7.25 (deb)

Steps:

• install maria db server on ubuntu
• connect antares to the local server

Actual results:

• You get error popup after connecting "TypeError: Cannot read properties of null (reading 'includes')".

• When creating new DB the collations dropdown is empty

• From there a lot more things go wrong as the dude above described...

BUT it somehow works fine when used over ssh. Similar setup, different environment.

[vl-ivanov]

I can confirm the same issue on Ubuntu 24.04 and Antares 0.7.28

[SmileYzn]

@Fabio286

About this issue, more one info:

When you access database directly via fixed IP like, 173.220.174.95 the Antares-SQL do not give more closed connection issues. But if you access across DNS domains that error appears after some time of inactivity in Antares-SQL.

I really stuck on this with Antares-SQL 🤣

Thanks 🙏