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

fix(TestScheduler): stop sorting actual results #473

Merged
merged 1 commit into from
Oct 7, 2015
Merged

fix(TestScheduler): stop sorting actual results #473

merged 1 commit into from
Oct 7, 2015

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Oct 7, 2015

  • fixes an issue where actual results were being sorted when they should not have been
  • ensures rescheduled Actions will be added to subscription and torn down when appropriate
  • uses state to convey notification information to action work function rather than closure

closes #422

@benlesh
Copy link
Member Author

benlesh commented Oct 7, 2015

I'm going to merge this one right away, since it fixes critical bugs with the test scheduler.

- fixes an issue where actual results were being sorted when they should not have been
- ensures rescheduled Actions will be added to subscription and torn down when appropriate
- uses state to convey notification information to action work function rather than closure

closes #422
@benlesh benlesh merged commit 51db0b8 into ReactiveX:master Oct 7, 2015
var c = cold( '----c---c---c---c---(c|)');
var d = cold( '----(d|)' );
var e1 = hot('a---b-----------c-------d-------|' );
var expected = '----a---(ab)(ab)(ab)c---c---(cd)c---(c|)';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It finally looks like it should. (ab) 👍

@benlesh benlesh deleted the fix_testscheduler branch April 27, 2016 17:15
@lock
Copy link

lock bot commented Jun 7, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Merge semantics for race conditions between synchronous notifications
2 participants