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

Multi app run does not understand dependencies and ordering - leads to timing issues #1435

Open
paulyuk opened this issue Jul 22, 2024 · 6 comments
Labels
kind/bug Something isn't working
Milestone

Comments

@paulyuk
Copy link

paulyuk commented Jul 22, 2024

Expected Behavior

Ideally multi app run files dapr.yaml understand DependsOn or priorities of dependencies so we can avoid issues like < dapr/quickstarts#1048 >.

@yaron2 suggest we assign to CLI maintainer for 1.15.

@m3nax
Copy link

m3nax commented Jul 23, 2024

I cannot debug my binding because it starts after the program that uses it and there is no way to wait for the binding to start.
Some ordering or something like docker-compose depends_on may be a good solution to implement.

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added stale and removed stale labels Aug 22, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Sep 21, 2024
@m3nax
Copy link

m3nax commented Sep 23, 2024

Not stale

@dapr-bot dapr-bot removed the stale label Sep 23, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added stale and removed stale labels Oct 23, 2024
@m3nax
Copy link

m3nax commented Oct 23, 2024

Not stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants