-
Notifications
You must be signed in to change notification settings - Fork 203
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
Comments
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. |
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. |
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. |
Not stale |
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. |
Not stale |
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.
The text was updated successfully, but these errors were encountered: