Bug #115627 Can't cancel connection attempts when the connected server has gone away
Submitted: 17 Jul 2024 10:42 Modified: 17 Jul 2024 13:01
Reporter: Kevin Johnston Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.38 OS:MacOS (Sonoma)
Assigned to: CPU Architecture:x86

[17 Jul 2024 10:42] Kevin Johnston
Description:
When a server that I have connected to has legitimately gone away, e.g. I have shut down the VM serving it, or disconnected from a VPN, Workbench repeatedly attempts to reconnect and I have to hit cancel multiple times in order to get to the end of the attempt cycle before it will let me close the relevant editor tab.

I encounter this issue multiple times a week as a web developer working on multiple projects that get brought up and shut down again throughout the day.
This prevents me from reaching other open editor tabs that I need to get to.
The only solution is to quit Workbench via the OS, but this is not ideal as I lose open query windows from other connectons. 

How to repeat:
Open a connection to a server that is currently reachable, but can be made to be unreachable e.g. a MySQL server running in a VM that can be stopped.

Outside of Workbench, make the MySQL server unreachable.

The connection dialog will appear. Click cancel. Repeatedly! Workbench will not allow any time to hit any other button before the dialog reappears.

Suggested fix:
Provide a button or method to allow users to force close a connection tab for when you know the connection can't be reached or when you simply don't need it open anymore.
[17 Jul 2024 12:38] MySQL Verification Team
Hello Kevin Johnston,

Thank you for the bug report.
This is most likely duplicate of Bug #95370, please see Bug #95370.

Regards,
Ashwini Patil
[17 Jul 2024 13:01] Kevin Johnston
Hello.
My bug has correclty been marked as a duplicate of #95370 but this is still an issue 5 years later so the original one has obviously been overlooked, as well as the other duplicate reported in #101149
When will this actually get addressed?