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

Setting Multiple Scheduled Events to Same Time Does Not Trigger in Deterministic Order #2625

Closed
arshamawan opened this issue Oct 19, 2018 · 1 comment · Fixed by #3331
Closed
Assignees
Labels

Comments

@arshamawan
Copy link

arshamawan commented Oct 19, 2018

Expected Behavior

We want the Scheduled Events, which fire at the same time, to activate in the same order in both online BTs and local.

Actual Behavior

They can happen the other way round.

@jaredbroad jaredbroad changed the title Reconciliation - Differences caused by SetHoldings and multiple ScheduleEvents Setting Multiple Scheduled Events to Same Time Does Not Trigger in Deterministic Order Oct 19, 2018
@mchandschuh
Copy link
Contributor

The underlying cause of this is that the scheduled events are stored in a concurrent dictionary which has non-deterministic enumeration behavior. We could add an index to each entry and sort them before invoking the handlers.

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 a pull request may close this issue.

3 participants