Note: Up to now I was only able to trigger the issue with a disabled metadata cache (STORAGE_USERS_FILEMETADATA_CACHE_STORE=noop) during testing. So this might not be relevant for production setups, that still needs to be analyzed. Nevertheless it's breaking some tests.
Describe the bug
When uploading a new file to a decomposedfs setup that initial upload already creates a revision duplicating the content of the upload.
Initial debugging indicates that when Finalizing the Upload we try to read the current node attributes from the metadata lockfiie instead of the the metadata file itself, when using the messagepack backend.
Note: Up to now I was only able to trigger the issue with a disabled metadata cache (STORAGE_USERS_FILEMETADATA_CACHE_STORE=noop) during testing. So this might not be relevant for production setups, that still needs to be analyzed. Nevertheless it's breaking some tests.
Describe the bug
When uploading a new file to a decomposedfs setup that initial upload already creates a revision duplicating the content of the upload.
Initial debugging indicates that when Finalizing the Upload we try to read the current node attributes from the metadata lockfiie instead of the the metadata file itself, when using the messagepack backend.