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(consumer): Runner#waitForConsumer uses consuming stop event instead of timers #724

Merged
merged 2 commits into from
May 29, 2020
Merged

Conversation

sempasha
Copy link
Contributor

fix #723

@sempasha
Copy link
Contributor Author

sempasha commented May 28, 2020

Could you, please, clarify ability of this PR will be merged and released next days?

@Nevon
Copy link
Collaborator

Nevon commented May 29, 2020

Thanks for fixing this. I somehow missed both the original PR and your comment yesterday.

Although I instinctively feel strange about making the runner an EventEmitter only so that it can listen to its own event, the solution is simple and contained enough that if we later decide to refactor it it's very easy to do so. As soon as the pipeline has run, I will merge, after which it will be available in a pre-release build.

@Nevon Nevon merged commit b13567d into tulios:master May 29, 2020
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.

Runner#stop takes too much time because of hardcoded 1000ms timer
3 participants