Description
Currently the code wrapping/calling the FileLister handler will return an io.EOF (indicating the end of the list) when the underlying handler returns 0 entries. I've come upon a situation where it is possible to return 0 entries in one batch, but still possibly have more entries to send.
Line 273 in 6d8540e
This was originally put there as a safeguard, in case the underlying FileLister code was ill-behaved and didn't properly return io.EOF.
I'd like to remove this check but wanted to post about it first to give others a chance to raise issues.