Checksum Matches Existing Object - Json submit endpoint

[brynnz22]

When trying to re-submit a JSON that was previously deleted from production, I encounter the error:

detail": "provided checksum matches existing object: {'checksums.type': 'sha256', 'checksums.checksum': '9eaece59f58b4d58008f2efcf556736c0f5a0cbe16311206d7f6b127e9cfc580'}

[dwinston]

There is a workaround — I can locate the past dagster job that sourced your submitted json and then re-run it (e.g. via the dagster dagit UI). However, I recognize that re-submitting is a legitimate use case, so I’d rather change the code to e.g. include a timestamp in the submission so that the resulting payload has a unique checksum.

[brynnz22]

Thank you @dwinston apologies for not reviewing this sooner. I attempted to resubmit a json just now that I had previously submitted and then deleted from MongoDb weeks ago and I get the same error:

{ "detail": "provided checksum matches existing object: {'checksums.type': 'sha256', 'checksums.checksum': '9eaece59f58b4d58008f2efcf556736c0f5a0cbe16311206d7f6b127e9cfc580'}" }

[eecavanna]

I'm posting this comment to confirm that the production Runtime API is currently at commit: 0c69b60

That commit comes after (on the main branch) the commit that introduced the fix for this issue, so I expect the fix to be present in the production Runtime API.

[dwinston]

plan: add an optional timestamp kwarg to

nmdc-runtime/nmdc_runtime/util.py

Line 85 in 21393c5

def drs_metadata_for(filepath, base=None):

, which will pass it to a optional-timestamp-kwarg-added

nmdc-runtime/nmdc_runtime/api/core/util.py

Line 31 in 21393c5

def sha256hash_from_file(file_path: str):

, so that the same content submitted at a different time generates a different checksum. Finally, add a str of the current time to the invocation at

nmdc-runtime/nmdc_runtime/api/endpoints/util.py

Line 435 in 21393c5

**drs_metadata_for(

.