Open PrangerStefan opened 3 years ago
Is this a simple case of enabling z7 support?
I'm not sure, if that's the error we are seeing in prod. When extracting the archive locally, you are using your local environment, unrelated to sapphire production.
The real culprit imho is Zip::DestinationFileExistsError
, which happens when unextracting in the archive in SubmissionExtractionService
. There might be two reasons for that:
Dir.tmpdir
as part of generating the extraction path. Dir.tmpdir
returns the path to the tmp dir of the system (usually /tmp
) Dir.tmpdir
does not ensure uniqueness, but simply returns the path.Dir.mktmpdir
gx-xxx
directories in /tmp
Dir.mktmpdir
.I've just reread the documentation on Dir.mktmpdir
. If we are passing in a block, the directory will get cleaned up once the block is completed. So no further cleanup actions would be required from our side.
- As far as I can tell, we currently do not properly cleanup the previously created extraction dirs, could you please verify in production? (I'm expecting to see several
gx-xxx
directories in/tmp
Definitely the case, saw about 5 dirs in there yesterday.
(Regarding the error: I guess the SO post lead me on the wrong track. I read something about proprietary software and thought that this must be it...)
Note to self: Keith asked about adding support for different decompression methods.
We have received the following error message:
downloading it and locally decompressing resulted in the following: