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

Timing problem in service_invocation quickstarts #1061

Open
joebowbeer opened this issue Jul 24, 2024 · 2 comments
Open

Timing problem in service_invocation quickstarts #1061

joebowbeer opened this issue Jul 24, 2024 · 2 comments
Labels

Comments

@joebowbeer
Copy link
Contributor

joebowbeer commented Jul 24, 2024

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)

@paulyuk
Copy link
Contributor

paulyuk commented Jul 29, 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

@paulyuk
Copy link
Contributor

paulyuk commented Jan 24, 2025

Heartbeat, CLI issue still open so nothing to do here yet

@paulyuk paulyuk added bug Something isn't working area/serviceinvoke blocked labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants