Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
bisync: another day, another set of integration test fixes #7795
bisync: another day, another set of integration test fixes #7795
Changes from all commits
7ecc1e7
a0ea81d
7d61df0
39eb229
47690fb
1e8d42f
0e12c78
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should only be necessary to set
X-Amz-Meta-Mtime
as the s3 backend turns it into themtime
metadata.So I'm not 100% sure what this is needed for.
I think the
serve s3
code is a bit confused about exactly which parameter to use so we should probably unconfuse it rather than make it worse!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's a test to reproduce:
If I remember correctly, I think the problem is that there are blocks like this which try
X-Amz-Meta-Mtime
first but fall back to usingmtime
:rclone/cmd/serve/s3/backend.go
Lines 307 to 321 in e9e9feb
And previously it was not always consistently saving the one it ended up using in memory.
And then there's also
Last-Modified
just to make things even more fun!rclone/cmd/serve/s3/backend.go
Lines 194 to 197 in e9e9feb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should probably fix
serve s3
to be consistent and use just one of these values, but I decided to cherry-pick your patch for v1.67 - thank you :-)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have now fixed this is a slightly different way in 39f8d03 to make it clearer what is going on rather than using the state of
item.src == nil
to signify metadata.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed this one in 76798d5 - I'd forgotten I hadn't merged your fix - sorry!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also needs to change
rclone/fstest/test_all/clean.go
Line 20 in 0735f44
Though maybe that one should say
{12,24}
to clean the old and the new!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I've cherry-picked this now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good fix, but it really needs a test. I try to keep the VFS coverage up as all these corner cases are really difficult to track down!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I'll try to add one! (Although FWIW, I found this because it was causing
TestSFTPRclone:
to fail!)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also btw, I am now seeing a bunch of
expecting X to have MkdirMetadata method: optional feature not implemented
andexpecting X to have SetMetadata method
errors that I'm pretty sure were not there before...maybe related to the recent--create-empty-src-dirs
change?https://pub.rclone.org/integration-tests/2024-05-13-010010/sftp-cmd.bisync-TestSFTPRclone-5.txt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. I've cherry picked this :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That should probably be
p = ""
to fit with rclone conventions, not 100% sure!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I copied this from here:
rclone/vfs/dir.go
Lines 163 to 172 in e9e9feb