MySQL Bugs: #115126: "report bug" bug

Bug #115126	"report bug" bug
Submitted:	25 May 2024 18:38	Modified:	28 May 2024 16:31
Reporter:	Dave Dyer	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.25	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:

#1 Trying to exit using the close box, there's a "mysql workbench encountered a problem" pop-up, which brought me here.  However, there is no information
at all about the possible nature of the problem.

#2 the "close" option dismissed the problem pop-up, but the app still
did not exit.

#3 Trying to exit with the file/exit menu presents a more informative 
problem report, ie: "no such table: changes", but it does NOT present
the option of sending a bug report, and the app doesn't exit.

#4 so in summary, there's no way to get the app to exit gracefully.

How to repeat:
unknown

Suggested fix:
#1 be consistent about the offer to report a bug showing the
nature of the bug.
#2 exit anyway!

Hello Dave Dyer,

Thank you for the bug report.
To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (--log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html)?

Regards,
Ashwini Patil

this was a onetime event, there's no way to repeat it.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug.
 
Thank you for your interest in MySQL.

This depends on some obscure and rare error, which is not the subject
of this report.  This report is about bugs in the error reporting and 
recovery mechanisms.

When I encounter a problem like this in my development process, the best way to tackle it is to make an experimental build with deliberate fault introduction.