Great to finally have a testcase for this! Note TokuDB may not be necessary to trigger the bug: early 5.6 version (prior to TokuDB) had the same assertion also. Another idea may be that it is a different bug (part of stack matches)
Great to finally have a testcase for this! Note TokuDB may not be necessary to trigger the bug: early 5.6 version (prior to TokuDB) had the same assertion also. Another idea may be that it is a different bug (part of stack matches)