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 various TCK tests, there is an expectation that a closed/errored stream be immediately reported as such to the subscriber - see, for example, this test:
onSubscribeLatch.expectClose("Should have received onSubscribe");
However, the spec does not specify whether a subscriber should immediately get these callbacks, or if it should get them after a call to Subscription.request()
Getting no callbacks until a request is a bit more consistent with the other stream callback behaviors
But, at a minimum, it seems like the TCK test should support the case where a Publisher does not call onError/onComplete until the Subscriber makes a Subscription.request
The text was updated successfully, but these errors were encountered:
In various TCK tests, there is an expectation that a closed/errored stream be immediately reported as such to the subscriber - see, for example, this test:
reactive-streams-jvm/tck/src/main/java/org/reactivestreams/tck/PublisherVerification.java
Line 533 in a625d3a
However, the spec does not specify whether a subscriber should immediately get these callbacks, or if it should get them after a call to
Subscription.request()
Getting no callbacks until a request is a bit more consistent with the other stream callback behaviors
But, at a minimum, it seems like the TCK test should support the case where a
Publisher
does not callonError/onComplete
until theSubscriber
makes aSubscription.request
The text was updated successfully, but these errors were encountered: