MySQL Bugs: #110786: Check for Update

Bug #110786	Check for Update
Submitted:	24 Apr 2023 16:48	Modified:	4 Jul 2023 13:53
Reporter:	Harry Towner	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.33, 8.0.34, 8.0.36, 8.0.38	OS:	MacOS (13.3.3)
Assigned to:	Marcin Marek	CPU Architecture:	ARM

Description:
When selecting Check for Updates under the Help menu tab a message appears stating:

Error
Unhandled exception:
'CheckForUpdateThread' object has no attribute 'isAlive'
Check the log for more details.

How to repeat:
If you select Check for Updates again, no pop-up window appears. In order to check again, you must quit SQL Workbench and execute again. Again the same issue happens (error and then if checked again - nothing)

I can confirm this issue happens.
MacBook Pro 13'', Apple Silicon M1, macOS Ventura 13.3.1

Similar to the issue with the previous version of MySQL Workbench 8.0.32 the only workaround is to AGAIN downgrade to the version 8.0.31.

I naively thought that these crashes will be fixed in this new version 8.0.33 as it was promised on the following bug report page, but note - here we go again:
https://bugs.mysql.com/bug.php?id=109671

The only difference, is that now I can at least execute queries without crashes.  MySQL Workbench "confidently" crashes each time I quite the application (⌘Q).

Bug #111788 marked as duplicate of this one.

UPDATE

Updated MySQL Workbench from version 8.0.33 to the just released version 8.0.34 - the issue is still present.

Bug #111874 marked as duplicate of this one.

Bug #111752 marked as duplicate of this one.

Bug #112623 marked as duplicate of this one.

Bug #112821 marked as duplicate of this one.

Bug #112938 marked as duplicate of this one.

Bug #113073 marked as duplicate of this one.

Bug #113158 marked as duplicate of this one.

I had the same issue in version 8.0.12 that I installed in 2018.

I thought the update was maybe broken because it was an old version.  So I installed 8.0.34 and I got the same error.

Notes:
- Reinstalling over my old installation did not seem to lose my settings (at least connection settings)
- It looks like even in my old version I get the same error message and identified cause in the log.  Maybe old code that point to a resource that is no more existing.

I am on version 8.0.32 and having this same issue.

This also appears on 8.0.36. Running on MPB M2 Max (Sonoma 14.3)

I can confirm this is still an issue on Windows 2022 Data Centre 21H2 on MySQL Workbench 8.0.36 Community (3737333 CE 64 bit)

Issue is happening for me as well on v8.0.36 build 3737333 CE (64 bit) Community
Microsoft Windows [Version 10.0.19045.4170]

I can confirm this still happens in Windows 11 Pro OS Build 22631.3374

MySQL Workbench version: 8.0.34 build 3263449 CE

Bug #114805 marked as duplicate of this one.

I can confirm this also happens in Ubuntu 24.04

MySQL Workbench version: 8.0.36 build 3737333 CE (64 bits)

Bug #115067 marked as duplicate of this one.

The new version 8.0.38 was releases 8 days ago and the issue is still present.
https://dev.mysql.com/doc/relnotes/workbench/en/news-8-0-38.html

Is it a record already - a bug that is present in the last 4 releases in a row?
Years come by - the bug persists.

What can I say - at least something is stable in this world.

I just subscribe to see for how long it would take MySQL Wrokbench to fix this bug.

Bug #115686 marked as duplicate of this one.

I just upgraded to 8.0.38 and this issue still exists.

Bug #115814 marked as duplicate of this one

Bug #115888 marked as duplicate of this one

Latest versions of Python changed the isAlive() attribute to is_alive(), edit the file C:\Program Files\MySQL\MySQL Workbench 8.0 CE\modules\wb_utils_grt.py and change line 725 and change line 728 for if self.json:

Latest versions of Python changed the isAlive() attribute to is_alive(), edit the file C:\Program Files\MySQL\MySQL Workbench 8.0 CE\modules\wb_utils_grt.py and change line 725 and change line 728 for if self.json:

Bug #115993 marked as duplicate of this one

Bug #116150 marked as duplicate of this one