-
Notifications
You must be signed in to change notification settings - Fork 523
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
Timing problem in service_invocation quickstarts #1061
Comments
This was referenced Jul 24, 2024
Hey @joebowbeer - agree this is a problem and we need some design so multiapp run can check for health and liveliness of sidecars. We have a 1.15+ item on Dapr CLI for this. dapr/cli#1435 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One timing problem that occurred when I ran the javascript/http example as a multi-run app in the devcontainer:
The order-processor may not be ready to receive the first order from the checkout service, in which case the first post returns a 500 and exits the checkout loop.
Moving the sleep to the top of the loop helps.
I think this problem and potential improvement applies to all of these multi-run service_invocation implementations, not just javascript.
Is there a better way for checkout to wait until the order-processor is running?
Originally posted by @joebowbeer in #536 (comment)
The text was updated successfully, but these errors were encountered: