Some of the cvxopt projects wheels are built using glpk version 4.65, which has a known bug that also affects rummikub-solver, in some as yet to be determined circumstances, including states using the default ruleset.
E.g. having the following 19 tiles on your rack and asking for an initial meld solution would trigger the crash, but this is just one example of several:
<Black 1 (1)> <Black 5 (5)> <Black 6 (6)> <Black 8 (8)> <Black 9 (9)>
<Black 10 (10)> <Black 12 (12)> <Black 12 (12)>
<Blue 2 (15)> <Blue 3 (16)> <Blue 4 (17)> <Blue 7 (20)> <Blue 9 (22)>
<Blue 9 (22)> <Blue 12 (25)>
<Orange 8 (34)> <Orange 10 (36)>
<Red 5 (44)> <Red 7 (46)>
The GLPK backend prints out the following text and dumps core:
glp_add_cols: ncs = 0; invalid number of columns
Error detected in file api/prob1.c at line 362
Fatal Python error: Aborted
The issue can be avoided by building the cvxopt project from source using either older (4.61 or earlier, it is unclear in what version between 4.62 and 4.65 the bug appeared) or newer GLPK versions.
Some of the cvxopt projects wheels are built using glpk version 4.65, which has a known bug that also affects rummikub-solver, in some as yet to be determined circumstances, including states using the default ruleset.
E.g. having the following 19 tiles on your rack and asking for an initial meld solution would trigger the crash, but this is just one example of several:
The GLPK backend prints out the following text and dumps core:
The issue can be avoided by building the cvxopt project from source using either older (4.61 or earlier, it is unclear in what version between 4.62 and 4.65 the bug appeared) or newer GLPK versions.