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
In this example, after 3 errors the subscriber switches to the alternative (empty) sequence correctly, but the original brokenStream sequence is continued being consumed non stop. It can easily be seen by writing a log inside the randomBreak function.
This bug is not reproducible when only retry or only onErrorResumeNext combinators are used. Using both causes the problem.
The text was updated successfully, but these errors were encountered:
Hi Guys,
found another bug that is critical from my point of view:
when using both .retry and .onErrorResumeNext combinators the "original" sequence is being consumed after error.
Example:
In this example, after 3 errors the subscriber switches to the alternative (empty) sequence correctly, but the original
brokenStream
sequence is continued being consumed non stop. It can easily be seen by writing a log inside therandomBreak
function.This bug is not reproducible when only
retry
or onlyonErrorResumeNext
combinators are used. Using both causes the problem.The text was updated successfully, but these errors were encountered: