Describe the bug
The constraint that no two operational datasets should exist with the same generated uid, seems to work well in development tests but fails in production.
To Reproduce
Register two datasets in MedPerf with the same generated uid. Have one dataset in development and one dataset operational. Then, run medperf dataset set_operational on the development dataset. This returns 400 bad request when using the development version of medperf (as expected), but returns 500 internal server error using the production version of medperf.
Expected behavior
It should also return 400 bad request in production.
Additional context
This could be related to the fact that we use sqlite3 database in development, but we use postgresql in production.
Describe the bug The constraint that no two operational datasets should exist with the same generated uid, seems to work well in development tests but fails in production.
https://github.com/mlcommons/medperf/blob/09edc70bcf7f1615c532c8f8b15f10de9b406e33/server/dataset/models.py#L39-L47
To Reproduce Register two datasets in MedPerf with the same generated uid. Have one dataset in development and one dataset operational. Then, run
medperf dataset set_operationalon the development dataset. This returns 400 bad request when using the development version of medperf (as expected), but returns 500 internal server error using the production version of medperf.Expected behavior It should also return 400 bad request in production.
Additional context This could be related to the fact that we use sqlite3 database in development, but we use postgresql in production.