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
Warning! Behavior change regarding handling illegal calls with null in Processors and Subjects.
The Reactive Streams specification mandates that calling onNext and onError with null should
result in an immediate NullPointerException thrown from these methods. Unfortunately, this requirement was overlooked (it resulted in calls to onError with NullPointerException which meant the Processor/Subject variants entered their terminal state).
If, for some reason, the original behavior is required, one has to call onError with a NullPointerException explicitly:
PublishSubject<Integer> ps = PublishSubject.create();
TestObserver<Integer> to = ps.test();
// ps.onNext(null); // doesn't work anymoreps.onError(newNullPointerException());
to.assertFailure(NullPointerException.class);
API changes
Pull 5741: API to get distinct Workers from some Schedulers.
Pull 5734: Add RxJavaPlugins.unwrapRunnable to help with RxJava-internal wrappers in Schedulers.
Pull 5753: Add retry(times, predicate) to Single & Completable and verify behavior across them and Maybe.
Documentation changes
Pull 5746: Improve wording and links in package-infos + remove unused imports.
Version 2.1.8 - December 27, 2017 (Maven)
Warning! Behavior change regarding handling illegal calls with
null
inProcessor
s andSubject
s.The Reactive Streams specification mandates that calling
onNext
andonError
withnull
shouldresult in an immediate
NullPointerException
thrown from these methods. Unfortunately, this requirement was overlooked (it resulted in calls toonError
withNullPointerException
which meant the Processor/Subject variants entered their terminal state).If, for some reason, the original behavior is required, one has to call
onError
with aNullPointerException
explicitly:API changes
Worker
s from someScheduler
s.RxJavaPlugins.unwrapRunnable
to help with RxJava-internal wrappers inScheduler
s.retry(times, predicate)
toSingle
&Completable
and verify behavior across them andMaybe
.Documentation changes
package-info
s + remove unused imports.Observable
marbles 11/28.Observable
(12/06).autoConnect()
JavaDoc + add its marble.@see
toCompletable
.retryWhen()
operators.BehaviorProcessor
JavaDoc.Bugfixes
TrampolineScheduler
not callingRxJavaPlugins.onSchedule()
, add tests for all schedulers.runnable == null
in*Scheduler.schedule*()
.buffer()
calling cancel unnecessarily.Subject
/FlowableProcessor
NPE fixes, addUnicastProcessor
TCK.Other
XOnSubscribe
parameter name toemitter
for better IDE auto-completion.The text was updated successfully, but these errors were encountered: