There are many methods in the metadata.py module that write to the file metadata file, to the point where some methods are causing bugs in others - see https://kbase-jira.atlassian.net/browse/PTV-1767 for an example.
It'd be much simpler if the metadata was generated once on file upload and then never touched again other than adding an UPA (unless corruption was detected on read, and then it should be regenerated, perhaps with a flag saying so).
Related to https://github.com/kbase/staging_service/issues/174
There are many methods in the
metadata.pymodule that write to the file metadata file, to the point where some methods are causing bugs in others - see https://kbase-jira.atlassian.net/browse/PTV-1767 for an example.It'd be much simpler if the metadata was generated once on file upload and then never touched again other than adding an UPA (unless corruption was detected on read, and then it should be regenerated, perhaps with a flag saying so).