[
https://issues.apache.org/jira/browse/AIRAVATA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743842#comment-17743842
]
ASF subversion and git services commented on AIRAVATA-3702:
-----------------------------------------------------------
Commit 335ee8a488b7d64ebd85bbd02019df8d4916d587 in airavata-django-portal's
branch refs/heads/AIRAVATA-3698--Add-support-for-Python-3.11 from Marcus
Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=335ee8a4 ]
AIRAVATA-3702 Update SDK for bug fix
> User input files renamed with random extension when experiment launched
> -----------------------------------------------------------------------
>
> Key: AIRAVATA-3702
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3702
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> When a user uploads an input file, that files goes into a staging directory
> (the user's "tmp" directory). If a user uploads two input files with the same
> name, the second one will be renamed with some random characters added to the
> end of the name (see
> https://docs.djangoproject.com/en/4.2/ref/files/storage/#django.core.files.storage.Storage.get_alternative_name).
> However, the original name of the file should be stored in the
> replica_catalog and when the file is moved out of the staging directory and
> into the experiment data directory, it should be renamed back to the
> original, user-supplied filename. That's failing to happen.
> Actually, it looks like the root of the problem is that the randomized
> filename is getting stored in replica_catalog.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
