Description
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I was using obstore library which uses this package and encountered an issue with weird paths in our object storage (azure) ( developmentseed/obstore#429 for reference ). We had some paths that contained double slash which is allowed by azure service. These kinds of paths throw an exception when listing contents of a container.
Describe the solution you'd like
It would be nice to be able to catch this exception or just ignore this and print warning as right now it stops the iterator from yielding paths. Maybe a flag? Or to have implementations for specific services allow these kinds of paths if the service allows them (like azure).
Describe alternatives you've considered
Unfortunately I can't always fix these paths as its coming from other teams so have to deal with messy data lake.
Additional context
(issue linked above)