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
This is a follow-up to #2125, this time targeting the same class of
discarding race but on `UnicastProcessor`.
As there is a chance that the race references `actual` (to resolve the
discard hook) AFTER `cancel()`, we need to keep that field populated.
It was nulled out for the benefit of `downstreamCount()` (see #980) so
we replace that by a boolean, set to true when subscribed.
Reviewed-in: #2126
This is a follow-up to #2125, this time targeting the same class of
discarding race but on `UnicastProcessor`.
As there is a chance that the race references `actual` (to resolve the
discard hook) AFTER `cancel()`, we need to keep that field populated.
It was nulled out for the benefit of `downstreamCount()` (see #980) so
we replace that by a boolean, set to true when subscribed.
Reviewed-in: #2126
Expected behavior
to print
0 1 0
Actual behavior
Prints
0 1 1
.This is due to the processor's
cancel()
method not clearing theactual
field, which in turn makesdownstreamCount()
return 1.Reactor Core version
3.1.2
The text was updated successfully, but these errors were encountered: