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

Copied the code from OperationMerge to fix synchronization #615

Merged
merged 1 commit into from
Dec 12, 2013

Conversation

abersnaze
Copy link
Contributor

for #614

@cloudbees-pull-request-builder

RxJava-pull-requests #549 SUCCESS
This pull request looks good

@benjchristensen
Copy link
Member

Amazing this made it almost a year (or more?) without us seeing a bug in prod. Thanks for catching and fixing.

benjchristensen added a commit that referenced this pull request Dec 12, 2013
Copied the code from OperationMerge to fix synchronization
@benjchristensen benjchristensen merged commit 6374bc8 into ReactiveX:master Dec 12, 2013
@abersnaze abersnaze deleted the issue614 branch December 13, 2013 01:03
rickbw pushed a commit to rickbw/RxJava that referenced this pull request Jan 9, 2014
Copied the code from OperationMerge to fix synchronization
jihoonson pushed a commit to jihoonson/RxJava that referenced this pull request Mar 6, 2020
…rHealthIn… (ReactiveX#615)

* Issue ReactiveX#607: The CircuitBreakerHealthIndicator and RateLimiterHealthIndicator should be disabled by default. Otherwise the application health status is DOWN when a CircuitBreaker is open which is not what users want.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants