NoMethodError when uploading dir instead of dir contents

[ryantate]

I think I hit a new bug in 1.1.0

This works fine:

ruby -I s3sync s3sync/s3sync.rb -r --ssl --delete testUploads/ myBucket:testUploads

But this produces an error:

ruby -I s3sync s3sync/s3sync.rb -r --ssl --delete testUploads myBucket:testUploadsParent

Notice the difference is the lack of trailing slash on the source dir, indicating I want the actual dir itself, not just its contents, uploaded to the destination dir.

The error, the sole output of the command, is:

s3sync/s3sync.rb:124:in `main': undefined method `[]' for nil:NilClass (NoMethodError)
        from s3sync/s3sync.rb:681

Not sure the cause of this. But if I replace my old version (1.0.13) of s3sync for the new one, everything works fine.

[ferrix]

Will take a look!

[ferrix]

Augh.. am I ever an idiot 

Fix coming.

[ryantate]

No worries! Glad to see so many new features in the new version!

[grempe]

I am also seeing a similar error with the latest build:

s3sync.rb:500:in `updateFrom': undefined method `closed?' for nil:NilClass (NoMethodError)
        from s3sync.rb:387:in `main'
        from s3sync.rb:690

I am running s3sync from a cron job with a command like this:

/usr/local/bin/ruby s3sync.rb -r --ssl --delete /home/backups/ bucket.name:/bucket.folder.name/backups

Any ideas?


PS - It would be awesome if you could put this all in a subversion repos so we could keep the code up to date more easily.  Or even better you could package it as a Ruby Gem!  (Try this for easy gem goodness! : http://drnicwilliams.com/2006/10/11/generating-new-gems/ ).

[ferrix]

I ran into this too this morning and quickly fixed it.  Try getting the tarball again and see if it's better for you as well.  I didn't even up the version for this, which is naughty I know.  But I'm supa busy today.

[lowflyinghawk]

you didn't up the version? shame on you! take yourself to the woodshed!

missing one of these points out how difficult it is be sure all your code is working.  after a long series of changes, all of which worked as far as I could tell, I tried listing an empty bucket. boing! wrong number of arguments error in a logging function!  I thought I'd covered them all by manually editing the code and causing the error side of conditionals to execute, but I was wrong about that.

[ferrix]

This is the secret (sshhh don't tell) to why I like to foster the s3sync community and don't overtly ask anything in return.  It is really hard to catch all my own bugs 

[lowflyinghawk]

yes, the perversity of users is well known to be unbounded, that's why big projects use betas (of course this doesn't include S3, they just roll it out and pray)