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
When using the run command, it's not possible to process files which have a # in their names (which is a valid character in S3), as they are interpreted as inline comments.
It's not possible to escape them either, as the \ is passed on to S3.
Example with file s3://dummy/foo/test \#3 /bar.jpg (filenames were removed) :
$ s5cmd --dry-run run test
mv s3://dummy/foo/test \#3 /bar.jpg s3://dummy/foo/test \#3/bar.jpg
$ s5cmd --log debug run test
ERROR "mv s3://dummy/foo/test \\#3 /bar.jpg s3://dummy/foo/test \\#3/bar.jpg": NoSuchKey: The specified key does not exist. status code: 404, request id: DJQNRYQN42QTWC7E, host id: YF1dXLn/wFe7VXNidbR8KCgZVRWqYdtpLmnvDDM9WfIGVSq3egUslUjQ8lgOlRnAON1B0Rkgr3Y=
The text was updated successfully, but these errors were encountered:
Previously s5cmd supported a command with an inline comment like `ls s3://bucket/object.gz # inline comment` was supported.
Comment per line is still supported.
Fixes#309
* command/run: drop inline comment support
Previously s5cmd supported a command with an inline comment like `ls s3://bucket/object.gz # inline comment` was supported.
Comment per line is still supported.
Fixes#309
* e2e/run: fix test case
* changelog: fix wording
When using the
run
command, it's not possible to process files which have a#
in their names (which is a valid character in S3), as they are interpreted as inline comments.It's not possible to escape them either, as the
\
is passed on to S3.Example with file
s3://dummy/foo/test \#3 /bar.jpg
(filenames were removed) :The text was updated successfully, but these errors were encountered: