Closed franga2000 closed 1 year ago
The quick solution should be to add avoid_conflicts
to BASE_DEFAULT_OPTIONS
in draw/generator/common.py:161
.
Encountered the same issue, made a similar quick fix it by removing "avoid_conflicts"
from get_relevant_options
in BaseDrawManager
:
diff --git a/tabbycat/draw/manager.py b/tabbycat/draw/manager.py
index b59216797..8e976972c 100644
--- a/tabbycat/draw/manager.py
+++ b/tabbycat/draw/manager.py
@@ -62,7 +62,7 @@ class BaseDrawManager:
def get_relevant_options(self):
if self.teams_in_debate == 'two':
- return ["avoid_institution", "avoid_history", "history_penalty", "institution_penalty", "pullup_debates_penalty", "side_penalty", "pairing_penalty", "avoid_conflicts"]
+ return ["avoid_institution", "avoid_history", "history_penalty", "institution_penalty", "pullup_debates_penalty", "side_penalty", "pairing_penalty"]
else:
return []
I have no idea if this breaks another draw type or something else - I'm basically reverting part of 32b30338daf248f20c88b4ba8c26c57df083c68e. I guess that's karma for using a dev version.
Running: a1ca1a390866199e1884db12c215ddaa867a98dc
When generating the draw for the first elimination round in a WS tournament, I encountered this exception:
I quickly patched around it like so and we manually confirmed the draw was correct:
Of course, this is not a fix for the problem, just avoiding the symptoms. I intend to find the cause of this issue and fix it in the following days, bu I'm dropping an issue here so I don't forget