Sync occurs despite the fact that the contents haven't changed

[rodriguezsergio]

I have a daemon watching a directory that subsequently calls aws s3 sync s3://bar, but I'm surprised to still see

upload: foo to s3://bar
Completed 1 part(s) with ... file(s) remaining

even though the contents haven't changed. The only change in the file has been the file's last modification time. Unfortunately, I don't see any options in the documentation to have s3 ignore file attributes, so I'm wondering if there is a chance that such a feature will be implemented in the near future?

[jamesls]

There's a write up of this problem here: #599

We're still looking into the best ways to address this, but I think as a first step, we should implement the --size-only argument from #473. This would help alleviate some (but not all) of the issues.