Skip to content
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

1.x: fix filter() default-requesting and thus going unbounded #3912

Merged
merged 1 commit into from
May 5, 2016

Conversation

akarnokd
Copy link
Member

@akarnokd akarnokd commented May 5, 2016

Forgot that Subscriber defaults to requesting Long.MAX_VALUE unless suppressed and apparently there was no verification of filter's backpressure behavior; the two existing tests didn't really check for the delivery pattern.

@stevegury
Copy link
Member

👍
I think the bug is serious enough that we should release a new version ASAP.

@akarnokd
Copy link
Member Author

akarnokd commented May 5, 2016

Agree. Not sure if you can release with 1.1.4.1 or you have to roll to 1.1.5.

@akarnokd akarnokd merged commit cac7430 into ReactiveX:1.x May 5, 2016
@akarnokd akarnokd deleted the FilterDefaultRequestFix branch May 5, 2016 19:29
@JakeWharton
Copy link
Contributor

Does map need the same change?

@akarnokd
Copy link
Member Author

akarnokd commented May 5, 2016

No. Map doesn't set the Producer on this so no default-request happens.

@JakeWharton
Copy link
Contributor

Ah, that's right. I think I made the same mistake on the first PR, too.

On Thu, May 5, 2016 at 3:32 PM David Karnok [email protected]
wrote:

No. Map doesn't set the Producer on this so no default-request happens.


You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#3912 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants