You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If a user is deleting an uploaded file from the inbox, it is correctly removed by lega-commander/TSD in co-operation, but the proper "remove" message to CEGA is not having the intended effect. I.e. CEGA still lists the file as available for user to pick for ingestion (when defining a Run or DataSet in the submission portal).
A "remove" message is being sent (seen in the logs), unknown if:
if the format conforms to the json schema for this message type
if a proper correlationID is set for the message (CEGA known to fail/ignore messages without a mandatory correlationID)
if all fields of the message has the proper content. Both fileSize and lastModified fields are set to value "0" which probably should be corrected.
Expected behavior
When the delete end-point is executed, a properly formatted message with correct content is sent to CEGA from the proxy service (similar pattern to the upload message when the upload end-point is utilized)
The text was updated successfully, but these errors were encountered:
Describe the bug
If a user is deleting an uploaded file from the inbox, it is correctly removed by lega-commander/TSD in co-operation, but the proper "remove" message to CEGA is not having the intended effect. I.e. CEGA still lists the file as available for user to pick for ingestion (when defining a Run or DataSet in the submission portal).
A "remove" message is being sent (seen in the logs), unknown if:
Expected behavior
When the delete end-point is executed, a properly formatted message with correct content is sent to CEGA from the proxy service (similar pattern to the upload message when the upload end-point is utilized)
The text was updated successfully, but these errors were encountered: