-
Notifications
You must be signed in to change notification settings - Fork 496
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
[WebToolsE2E] Using CLI, dotnet new Aspire Starter App and dotnet run, then wait for 30 seconds, we will see a warning saying it failed to get the dashboard logs #3612
Labels
area-app-model
Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
Milestone
Comments
Is it consistent? |
I can reproduce. |
davidfowl
added
area-app-model
Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
and removed
area-dashboard
labels
Apr 12, 2024
davidfowl
added a commit
that referenced
this issue
Apr 12, 2024
- When the dashboard was running as an executable, the logic we used to detect replics in broken. Instead of trying to be clever, watch all dashboard resources and log their output. This is more robust and future proof as we only have one dashboard running at once. - Deleted the timeout Fixes #3612
github-actions bot
pushed a commit
that referenced
this issue
Apr 12, 2024
…cutable, the logic we used to detect replics in broken. Instead of trying to be clever, watch all dashboard resources and log their output. This is more robust and future proof as we only have one dashboard running at once. - Deleted the timeout Fixes #3612
davidfowl
added a commit
that referenced
this issue
Apr 12, 2024
- When the dashboard was running as an executable, the logic we used to detect replics in broken. Instead of trying to be clever, watch all dashboard resources and log their output. This is more robust and future proof as we only have one dashboard running at once. - Deleted the timeout Fixes #3612
github-actions bot
pushed a commit
that referenced
this issue
Apr 12, 2024
…cutable, the logic we used to detect replics in broken. Instead of trying to be clever, watch all dashboard resources and log their output. This is more robust and future proof as we only have one dashboard running at once. - Deleted the timeout Fixes #3612
danmoseley
pushed a commit
that referenced
this issue
Apr 12, 2024
Fixes #3612 Co-authored-by: David Fowler <davidfowl@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
REGRESSION INFO: This is a new feature on Aspire 8.0.0-preview.6.24210.28
INSTALL STEPS
1.Clean machine: Win11 x64 23h2 ENU
2.Install SDK 8.0.204 (latest-released-build)
3.Install Aspire 8.0 P6 workload version 8.0.0-preview.6.24211.5, apply feeds
REPRO STEPS
dotnet new aspire-starter -o AspireStarterApp03
cd AspireStarterApp03\AspireStarterApp03.AppHost
dotnet run
ACTUAL
We will see a warning saying it failed to get the dashboard logs
Before opening the URL of the dashboard in the browser, I was doing something else. When I came back to open the URL, I see this warning which is a bit confusing.
EXPECTED
The warning message should be more clear about what timed out and after how long
The text was updated successfully, but these errors were encountered: