ArtifactFileField's validation is too strict
ArtifactFileField validates that the file being saved does not already exist in Artifact storage0. However, when bulk_get_or_create encounters a problem during bulk_create, it already moves the file into place before falling back to saving each model individually1. As a result, the validation logic from ArtifactFileField throws a ValueError because the file is already in Artifact storage, however it is still not saved to the database.
The validation should allow the file to be already in Artifact storage as long as it's being "saved" to the exact same location as it is at already.
Please register to edit this issue