Open dchackett opened 6 years ago
This issue may have been resolved unintentionally. As a test, I ran the example "cu_multirep_hmc.py" twice in a row. cu_multirep_hmc.py specifies 18 total tasks. Running the example a second time added the same 18 tasks to the dispatch DB without any collisions, and added an additional two taxis to the pool DB without any collisions. The taxis ran and completed the tasks without complaint.
Leaving the issue open pending performing another test: adding additional tasks to an existing dispatch DB, which can probably become a new example.
Having a run-specification script open an existing dispatch DB is currently only partially implemented and tends to break. In taxi 0.1, it threw an error if you tried to initialize a new dispatch DB on top of an existing one. Override behavior was just clobbering the existing DB and starting fresh.
What do we want the behavior to be? Is there any sensible behavior to implement other than clobbering that won't let a user run a run-specification script on top of an existing dispatch DB and accidentally do every task twice?