Killing and restarting a run after moving files breaks the ability to sync that specific directory

[tatyree]

I moved some files while a sync run against a specific directory was taking place and so needed to restart the run to pick up the changes. I CTRL-C'd the run. When I went to restart s4cmd, it refused to run, throwing this error:

[Invalid Argument] Invalid number of parameter

This is the command that was killed:

export S4CMD_NUM_THREADS=8; s4cmd sync -rs <full local path>/* s3://<bucket>/<existing path>/

Running any other command, or this command against a different local path, works.

This is the --debug output:

  (D)s4cmd.py:494  read S3 keys from $HOME/.s3cfg file
  (D)s4cmd.py:170  >> sync_handler(<__main__.CommandHandler object at 0x103559910>, ['sync', '<full local path to>.jpg', 's3://<bucket>/<existing target path>/'])
  (D)s4cmd.py:170  >> validate(<__main__.CommandHandler object at 0x103559910>, 'cmd|s3,local|s3,local', ['sync', '<full local path but without trailing slash and filename>', '<full path to>.jpg', 's3://<bucket>/<existing target path/'])
  (E)s4cmd.py:182  [Invalid Argument] Invalid number of parameters

[rozuur]

This happens due to glob expansion in bash.
s3cmd sync -rs <full local path>/* expanded to multiple files '<full local path but without trailing slash and filename>', '<full path to>.jpg'

And that is the reason an error message related to Invalid Argument is thrown.