Skip to content
This repository has been archived by the owner on May 29, 2024. It is now read-only.

Make sure events are returned in the correct sequence order. #75

Merged
merged 1 commit into from
Apr 8, 2016

Conversation

enriquein
Copy link
Contributor

This prevents Expected an event with sequence number N. exceptions. I used to get these exceptions in about 3-5% of the emitted commands. This seems to fix it.

Here's a more detailed explanation of my issue: http://stackoverflow.com/questions/36487655/cirqus-expected-an-event-with-sequence-number-0-exception

This prevents "Expected an event with sequence number N." exceptions.
@mookid8000
Copy link
Owner

oh shit that was a good catch!! thanks, man! 👍 ⚡

@mookid8000 mookid8000 merged commit e86bad8 into mookid8000:master Apr 8, 2016
@mookid8000
Copy link
Owner

I'll see to it that your fix gets released immediately

@enriquein
Copy link
Contributor Author

Much appreciated 😄

@mookid8000
Copy link
Owner

yeah - that must have bothered you 😨

@mookid8000
Copy link
Owner

it's out in 0.67.1 as soon as the build server finishes running tests and packing

@mookid8000
Copy link
Owner

it's out now 😁 thanks 👍

@enriquein
Copy link
Contributor Author

That was super fast. Thanks!

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.

None yet

2 participants