We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm glancing through the class and I see a few places where subscriptions is accessed outside its synchronization guard:
subscriptions
SubscriptionImpl.request()
checkSend
getAvailable
singalError()
removeIf()
request(Long.MAX_VALUE)
In addition, since request() may run concurrently with an onNext() emission, there is a risk of concurrent execution of the onXXX methods.
request()
onXXX
The text was updated successfully, but these errors were encountered:
thanks, I will investigate soon! sorry for the delay
Sorry, something went wrong.
No branches or pull requests
I'm glancing through the class and I see a few places where
subscriptions
is accessed outside its synchronization guard:SubscriptionImpl.request()
callscheckSend
which callsgetAvailable
which loops oversubscriptions
singalError()
is also called here which runsremoveIf()
request(Long.MAX_VALUE)
multiple times is completely legal with RS (although pointless).subscriptions
In addition, since
request()
may run concurrently with an onNext() emission, there is a risk of concurrent execution of theonXXX
methods.The text was updated successfully, but these errors were encountered: