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

Issue 1603 #1605

Merged
merged 1 commit into from
Jul 3, 2017
Merged

Issue 1603 #1605

merged 1 commit into from
Jul 3, 2017

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented Jun 7, 2017

Change the observable value returned when the command was unsubscribed from an error to an empty value. This fixes #1603.

@atoulme atoulme force-pushed the issue_1603 branch 3 times, most recently from de981fa to 59aa32c Compare June 7, 2017 17:00
@stevenchurd
Copy link

Thanks @atoulme, unfortunately I'm not especially familiar with the Hystrix command state machine. It certainly seems like it's an invalid assumption that a command never unsubscribes before being run but hopefully someone that knows more can weigh in as well. @mattrjacobs?

@mattrjacobs
Copy link
Contributor

@atoulme Apologies for the delay in getting to this - I was out on vacation. I agree that your fix is correct. If the compareAndSet returns false, that implies that the command has been unsubscribed, therefore the valid emission is nothing (not an error object as occurs today in master).

Nice find, and thanks for the PR!

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.

java.lang.RuntimeException: unsubscribed before executing run() with request caching enabled
3 participants