You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.
This is related to NBISweden/sda-cli#161. Similarly to what's suggested there out of niceness, server side this should be done to limit what can get passed on to the various backends.
I don't have any opinion on whatever this should be done in the storage backends (which presumably knows better what characters need to be removed) or in the main code (which might be simpler and might as well remove anything "weird").
With the currently deployed version for BP with the current sda-cli release, it seems uploading when giving a full path (e.g. sda-cli -c s3cmd.conf -r C:\some\thing) breaks because the backend storage does not like the generated object paths.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is related to NBISweden/sda-cli#161. Similarly to what's suggested there out of niceness, server side this should be done to limit what can get passed on to the various backends.
I don't have any opinion on whatever this should be done in the storage backends (which presumably knows better what characters need to be removed) or in the main code (which might be simpler and might as well remove anything "weird").
With the currently deployed version for BP with the current
sda-cli
release, it seems uploading when giving a full path (e.g.sda-cli -c s3cmd.conf -r C:\some\thing
) breaks because the backend storage does not like the generated object paths.The text was updated successfully, but these errors were encountered: