Jon Frisby

Ok. Re-running (twice) against a clean sub-folder produces the same behavior of the data being re-synced. So it seems to be either an issue on the S3 side, not something...

``` % ls -la ~/personal/Finance/AWS_Billing_Data/cur/billing_and_usage/20210101-20210201/20210123T082656Z/billing_and_usage-Manifest.json -rw-r--r-- 1 jonathonfrisby staff 6458 Jan 23 2021 /Users/jonathonfrisby/personal/Finance/AWS_Billing_Data/cur/billing_and_usage/20210101-20210201/20210123T082656Z/billing_and_usage-Manifest.json ``` An example of the details of one object that's getting re-synced.

@tim-finnigan Would it be helpful if I gave you access to the relevant S3 bucket?

I've identified the problem. I had AWS configured to put billing and usage reports under the prefix "/cur/". That got interpreted as a directory entry named "/" holding a directory...

Yeah, this would be immensely handy... Actually, beyond that, a probability factor for any given request (list, fetch, etc) seeing the object during a specified window would be great for...

I didn't know what the intended behavior actually _was_, so... If the intended behavior is as you say, then yes, that's what I'm reporting. See screenshot:

I have it turned on because I use it for other pages where doing so is supported. It appears to be a global setting, so disabling it here is disruptive...

... and once you fix that you run into the fact that in v. 1.0, log_switch no longer has `LogSwitch::Mixin`.

Updating playful to use the newer log_switch version was easy enough, although fully validating it was difficult because of the ether poor state of the various test suites. I've forked...

It was immensely helpful, so thank you! Sent from my iPhone > On Sep 14, 2015, at 1:33 PM, Steve Loveless [email protected] wrote: > > Cool, glad playful at least...