RE: [Fwd: Bug #19187 [Csd->CRp]: ** CRITICAL **: myx_grt_value_as_int: assertion `value != NULL' failed]

Dave, 

> I'm not impressed with a bug tracking protocol that closes a 
> bug because one person (Alfredo Kojima) failed to repeat it 
> on first try despite public record of at least two 
> occurrences, and with no attempt to elicit further details of 
> how to repeat.

I'm not sure what your problem is with that. First, what you see is very often not what actually happens behind the scenes. Alfredo is just the face in this situation, but there are other developers, support people etc. that work together with us developers to reproduce bugs and find solutions. Second, Alfredo is not any person but one of the GUI developers and actually *the* maintainer of the Linux part, so he knows the most about it. And if he cannot reproduce it then it is quite likely the bug is already fixed (although not always, of course). Third, your bug report wasn't impressive either. Have you actually tried to reproduce the problem more than once? Can you see it 100% of the time? Or how often do you see it? Have you tried another machine/another distro? Forth, Alfredo did not just close the bug but he also requested you to test our current release and what you can do to improve the bug report if you still see the problem. Isn't that exactly what you want to see?

> This kind of artificial bug-squashing statistics fiddling 
> doesn't fall within the bounds of acceptable ethical behaviour IMHO.

I understand your frustration. You want that beast fixed and we are here to fix it. But please understand also that this bug is one of many and we have a lot of work to do. So if a bug seems to be fixed then we rather spend our time to fix other bugs instead of doing two other rounds of communication just to confirm that the bug is either really fixed or is still present in an older release.
 
> I definitely *won't* be trying 1.0.6beta or any other beta.

Please reconsider this. We need your help and your patience. If you can still reproduce the problem we will be happy to reopen the issue report and will work until we get it fixed. 

Best regards,

Mike
--
Mike Lischke, Software Engineer GUI
MySQL AB, www.mysql.com


> [26 Apr 21:27] Alfredo Kojima
> 
> I was not able to reproduce the bug either in 1.0.5beta 
> neither with the latest release.
> If the bug persists with 1.0.6beta, please reopen this and 
> post the output when running as:
> export DEBUG=1
> mysql-workbench


-- 
MySQL GUI Tools Mailing List
For list archives: http://lists.mysql.com/gui-tools
To unsubscribe:    http://lists.mysql.com/[email protected]