Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AzureFileShareService fails to upload a directory if path does not already exists on the shared storage #505

Closed
motus opened this issue Sep 7, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@motus
Copy link
Member

motus commented Sep 7, 2023

e.g. the following directory upload fails:

{
    "from": "environments/apps/mysql/scripts/remote/common/",
    "to": "$experiment_id/$trial_id/scripts"
}

if path $experiment_id/$trial_id/ does not already exist on the file share.

Uploading a single file works, though - and I currently use it as a workaround, e.g.:

{
    // FIXME: A workaround for the bug in Azure FileShare Service.
    // Copy one known local file to trigger `mkdir -p` on the file share.
    "from": "environments/apps/mysql/scripts/remote/common/common.sh",
    "to": "$experiment_id/$trial_id/scripts/common.sh"
},
{
    "from": "environments/apps/mysql/scripts/remote/common/",
    "to": "$experiment_id/$trial_id/scripts"
}

@eujing want to look at it?

@motus motus added the bug Something isn't working label Sep 7, 2023
motus pushed a commit that referenced this issue Sep 7, 2023
Fix for #505 when parent folders do not exist in the remote file share
yet during an upload.

Co-authored-by: Eu Jing Chua <eujingchua@microsoft.com>
@bpkroth bpkroth closed this as completed Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants