You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2019. It is now read-only.
If an exception occurs on a fileSystem.read(s), then the whole chain will stop with an onError emission preventing us from getting subsequent files on the path.
One way around it, I think, would be to wrap the read in a flatMap() and emit an empty or special type empty buffer. Something like:
The current
readAll()
implementation inFSAllReader
fails if there is an exception reading a single file in the path. In this code:If an exception occurs on a
fileSystem.read(s)
, then the whole chain will stop with an onError emission preventing us from getting subsequent files on thepath
.One way around it, I think, would be to wrap the read in a
flatMap()
and emit an empty or special type empty buffer. Something like:Then we can let the caller decide what to do with the
ExceptionBuffer
. Would something in this direction work?The text was updated successfully, but these errors were encountered: