New release on its way; check announce board.

I'm going to try to get to this this weekend.

It may be counter-intuitive but by design once retries are exhausted it means give up.

But there should probably be an explicit stop error when this occurs.

OK, this is going to actually be a big deal.  The underlying aws ruby code changed a bunch.  working on it...

Wow holding that date constant just totally messed with me.  Thanks for the help!

Link I find to the dev guide is: http://developer.amazonwebservices.com/connect/entry.jspa?entryID=123
which still says 2006.  Halp?  Can you post the link?

Feel like an idiot but I still see the 2006 version:
http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=48

Am I missing something?  Where is the updated one?

Thanks for the info.. They updated it like THE VERY DAY after I checked.

Last I looked their API docs haven't been updated.  Anyone know if there's some official way to deal with this?  I'd rather not code based on empirical results.

I don't have one of those buckets but I'm guessing that the server name might be different?  You can set that via the env variable AWS_S3_HOST (defaults to s3.amazonaws.com)

I don't know the answer, but I just wanted to say that I read your post and am not ignoring you

I have nothing against that idea.  It should be possible to get a fixed number of worker threads going instead of having the comparator wait on one thing at a time.

"testing" is probably a directory node not a file node.  But that's beside the point.

I suppose the alternation in the regex (the pipe symbol) must be grouping wrong.
Maybe "\.svn(/|$)"

The idea of the last part is to say "slash, or end of string".  In other words match it when there's more after the .svn or when the "n" is the last character of the whole string.

Didn't test this, just thought experiment.

I agree that behavior doesn't seem to be beneficial

"(?:__XB/|@eaDir/|thumbs.db|<[A-Za-z0-9]+><.>CR2)"

I'm not sure what you are trying to do above with all the angle brackets... Maybe you were looking at some strange dialed of regex. 

In regex dot "." means any character.  * means "zero or more of"

I think what you might have wanted to say at first was ".*CR2"
which says "zero or more of any character followed by CR2"

maelcum's example will exclude anything that contains the characters CR2 preceded by one wildcard character.  What he should probably do for his log files is like "[.]log"

Because when you put period inside character class brackets it means really dot.  You can also escape stuff with backslashes
so like
\.log

If your command shell is complaining or doing bad things with all these special characters like * $ etc. try using single quotes for wrapping the regex string instead of doubles.  In many interpreters, single quotes mean "leave this string alone"