Input-S3 Plugin - Logic flaw with sincedb file

I'm having some problems with the input-s3 plugin missing files in my bucket and causing my entire pipeline to stall out (I'm doing batched processing and use the emptying of the source bucket as an indicator of being finished). I'd appreciate anyone that could take a look at and see if you agree with my analysis of the logic bug in the sincedb portion of this plugin.