We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm submitting a ... (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting [x] feature request
Scope (check one with "x")
[x] @zetapush/cli [ ] @zetapush/cometd [ ] @zetapush/client [ ] @zetapush/create [ ] @zetapush/platform [ ] @zetapush/worker
Current behavior In the integrations test, we use "waitForWorkerUp" which resolve when worker is up
Expected behavior waitForWorkerUp should resolve when worker is up and all onApplicationBoostrap are terminated
What is the motivation / use case for changing the behavior? The branch feature/adding-tests will be mergeable once waitForWorkerUp will be fixed
The text was updated successfully, but these errors were encountered:
damienld22
No branches or pull requests
I'm submitting a ... (check one with "x")
Scope (check one with "x")
Current behavior
In the integrations test, we use "waitForWorkerUp" which resolve when worker is up
Expected behavior
waitForWorkerUp should resolve when worker is up and all onApplicationBoostrap are terminated
What is the motivation / use case for changing the behavior?
The branch feature/adding-tests will be mergeable once waitForWorkerUp will be fixed
The text was updated successfully, but these errors were encountered: