You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
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: