You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I received a bug report over at mysql-native that I've tracked down to an assert failure in eventcore. It wasn't clear at first because there's another mysql-native issue that was covering up this assert failure during stack unwinding.
To reproduce:
Use the test case provided in the original post here
Edit mysql-native's source/mysql/protocol/sockets.d and comment out line 121: assert(!!socket); (I think it was supposed to be assert(socket !is null); but I'm getting a weird compile error from that - still figuring that one out) This change will allow the original AssertError to propagate to the top without being hijacked by mysql-native freaking out.
Nevermind the above post, I think my diagnostic code there is in error.
In any case, the corresponding mysql-native issue has made it clear that this was indeed a mysql-native issue after all, so I'm closing this. Thanks for the help, Sonke!
I received a bug report over at mysql-native that I've tracked down to an assert failure in eventcore. It wasn't clear at first because there's another mysql-native issue that was covering up this assert failure during stack unwinding.
To reproduce:
Use the test case provided in the original post here
Edit mysql-native's
source/mysql/protocol/sockets.d
and comment out line 121:assert(!!socket);
(I think it was supposed to beassert(socket !is null);
but I'm getting a weird compile error from that - still figuring that one out) This change will allow the original AssertError to propagate to the top without being hijacked by mysql-native freaking out.Run
dub
and receive this:The text was updated successfully, but these errors were encountered: