MySQL Bugs: #89394: Workbench

Bug #89394	Workbench
Submitted:	25 Jan 2018 8:03	Modified:	15 May 2018 5:21
Reporter:	Shlomo Belleli	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.3.10 / 8.0.11	OS:	Windows (Microsoft Windows 7 Enterprise Service Pack 1)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\shlomob.L008717\AppData\Roaming\MySQL\Workbench\log\wb.log]

How to repeat:
NA

Suggested fix:
NA

wb.log

Attachment: wb.log (application/octet-stream, text), 7.50 KiB.

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 and change the status back to 'Open'.

Thank you for your interest in MySQL.

screen shoot when tring to open table to show her data

Attachment: mysql bug 89394.png (image/png, text), 242.91 KiB.

nect action - ignore

Attachment: mysql bug 89394 -2.png (image/png, text), 208.56 KiB.

update wb.log file

Attachment: wb.26.1.18.txt (text/plain), 7.34 KiB.

Thank you for the feedback, please attach here using the Files tab a dump file with create table and insert data statements (private if you wish), table which allows to repeat the issue reported.

this morning screen shot

Attachment: screen 28.1.18.png (image/png, text), 210.88 KiB.

table create

Attachment: sale.sql (application/octet-stream, text), 2.08 KiB.

table data

Attachment: sale.csv (application/vnd.ms-excel, text), 1.51 KiB.

Shlomo, please give us a step list of what you did exactly to trigger that error. Of course this shouldn't happen and we want to fix it, but with the informations you gave us so far we cannot reproduce the problem.

screen shot-0 6.2.18

Attachment: 89394-6.2.18.png (image/png, text), 235.40 KiB.

screen shot-1 6.2.18

Attachment: 89394-6.2.18-1.png (image/png, text), 244.10 KiB.

After a night when the workbench was left open
When trying to open any table editor, or browsing any table data
I get this Assertion error
BTW I don't have any disk G: in my computer

If I will push retry button I will get the next screen shot
when closing the workbench and reopen it , he will work fine.

Thank you for the feedback. I am not able to repeat this issue with the information provided , then we need a repeatable test case explained step by step otherwise we will assume is an issue specific to your environment. Thanks.

Hi
this bug happen over night when the app is stay open

at 23:59 no problem
at 00:002 (new day) the is a problem
look at the image I just loaded

screen shot 20.4.18

Attachment: MySql bug.png (image/png, text), 96.35 KiB.

Today was released WorkBench 8.0.11 RC (tab Development Releases) try it:

https://dev.mysql.com/downloads/workbench/

after install of version 8.0.11

Attachment: mysql bug 23.4.18.png (image/png, text), 208.95 KiB.

Now the version is 8.0.11 and not 6.3.10
as it was before after the time 00:00 passed 
and trying to select one of the tables, I got this error

Hello  Shlomo,

Thank you for the feedback.
I could not repeat the issue at our end using with MySQL workbench 8.0.11 version.
If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Thanks,
Chiranjeevi.

screen image

Attachment: mysql-bug.png (image/png, text), 271.67 KiB.

file-1

Attachment: WER1B7B.tmp.appcompat.txt (text/plain), 82.35 KiB.

file-2

Attachment: WERFC6.tmp.WERInternalMetadata.xml (text/xml), 3.34 KiB.

one more file (bib one) was sent to the sftp his name is:
WER1CF2.tmp.mdmp - Bug #89394

How to Reopen this bug , 
I sent you ore file here and with the FTP at 23/4/18

What about this bug?
it is annoying in daily work !
How can I reopen in Status field?