Quarry choose wrong GTP engine when trying to resume previously saved game
Bug #684236 reported by
Damir
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Baltix |
In Progress
|
Medium
|
Mantas Kriaučiūnas | ||
quarry (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: quarry
I tried to resume previously saved go-game and choose to use GnuGo engine as one of player. But quarry tries to use GRhino engine instead and fails because GRhino doesn't support go.
Looks like Quarry simply uses first registered GTP engine, as if I put GnuGo on first place in the engine list everything working just fine.
To post a comment you must log in.
Fixed upstream (as of ten minutes ago)
The problem was actually that Quarry attempted to intelligently filter GTP clients that couldn't play the appropriate game type from the list... then walked the unfiltered list counting steps to find the selected index. Rather than pass a filtered list up the chain to where it needs to be read, for now we just don't filter.