Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix DoOnEach ASYNC fusion triggering onNext signal twice #3045

Merged
merged 1 commit into from
May 23, 2022
Merged

Fix DoOnEach ASYNC fusion triggering onNext signal twice #3045

merged 1 commit into from
May 23, 2022

Commits on May 19, 2022

  1. Fix DoOnEach ASYNC fusion triggering onNext signal twice 

    This commit fixes the DoOnEachFuseableSubscriber to interpret any
upstream onNext as a fusion trigger in ASYNC mode (onNext(null)).

Furthermore, this commit fixes the Operators.MonoSubscriber handling of
FUSED case. Since that abstract operator only supports ASYNC fusion,
the FUSED_* states are renamed FUSED_ASYNC_*. In the drain loop, even in
FUSED case the operator emits t downstream where it should emit null
technically (again, because FUSED == ASYNC). This error is also fixed.

Fixes #3044.
    @simonbasle
    simonbasle committed May 19, 2022
    Configuration menu
    Copy the full SHA
    720cf03 View commit details
    Browse the repository at this point in the history