-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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.
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
flatMap with maxConcurrent value of 1 results in NPE if Observable emitting null is returned. #3998
Comments
This has been fixed in 1.1.3. Please make sure you use the latest version of RxJava. |
Thanks - I'm using this via RxVertx so let me see if I can upgrade the underlying RxJava version without breaking something else. Good to know it is fixed however. |
The other issue I have is that I'm using RxGroovy -- the most recent release there appears to be 1.0.3 -- is this compatible with the 1.1.x releases of RxJava (it's |
They were some removals but I don't know much about RxGroovy. I suggest you talk to them about upgrading. |
Do you know who they are? There is an issue for the upgrade which has been around since Feb and the contact info is the same as the main RxJava project. I'm happy to do the update and submit a PR, but I'm not sure if there is anyone to review/merge it if I do. |
I have the rights to merge and @zsxwing is there to, but can't give any promise on releasing anything. You could also fork RxGroovy and release on your own terms to maven. |
Continued at ReactiveX/RxGroovy#13 |
The easiest way to reproduce this is as follows:
In this case the value from
Observable.just(null)
cannot be immediate emitted so it is queued. Since the observable is a scalar we queue the underlying value (in this casenull
) which results in a call tooffer
on the classSpscArrayQueue
. This class does not accept null element values so the result is an NPE.Removing the
maxConcurrent
argument fixes this, but unfortuantely in our case that's not possible as we need have a range that we need to run sequentially.The text was updated successfully, but these errors were encountered: