aspire: [WebToolsE2E][Aspire][Mac] Failed to launch the dashboard when Using VS Code to Debug Aspire App: 'Time out while waiting for the dashboard to be responsive'.

REGRESSION INFO: Not repro on Aspire 8.0.0-preview.2.23619.3

INSTALL STEPS

Clean machine: MacOS Install VS Code[1.85.2] Install C# Dev Kit[1.3.8] Install SDK 8.0.200 Install Aspire Preview 3 latest build 8.0.0-preview.3.24080.10 Apply NuGet Feeds

REPRO STEPS

  1. Create .NET Project > .NET Aspire Application > give a name > Create
  2. Right-click xxx.AppHost name > Open In Integrated Terminal > dotnet run

Note: This issue is very unstable on Windows machine.

ACTUAL Run aspire project with error: ‘Time out while waiting for the dashboard to be responsive’ image fail: Microsoft.Extensions.Hosting.Internal.Host[11] Hosting failed to start Aspire.Hosting.DistributedApplicationException: Timed out after 00:01:00 while waiting for the dashboard to be responsive. at Aspire.Hosting.Dcp.ApplicationExecutor.WaitForHttpSuccessOrThrow(Uri url, TimeSpan timeout, CancellationToken cancellationToken) in //src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 307 at Aspire.Hosting.Dcp.ApplicationExecutor.CheckDashboardAvailabilityAsync(String delimitedUrlList, CancellationToken cancellationToken) in //src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 263 at Aspire.Hosting.Dcp.ApplicationExecutor.StartDashboardAsDcpExecutableAsync(CancellationToken cancellationToken) in //src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 239 at Aspire.Hosting.Dcp.ApplicationExecutor.RunApplicationAsync(CancellationToken cancellationToken) in //src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 92 at Aspire.Hosting.Dcp.DcpHostService.StartAsync(CancellationToken cancellationToken) in //src/Aspire.Hosting/Dcp/DcpHostService.cs:line 65 at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token) at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func3 operation) Unhandled exception. System.AggregateException: One or more errors occurred. (Timed out after 00:01:00 while waiting for the dashboard to be responsive.) ---> Aspire.Hosting.DistributedApplicationException: Timed out after 00:01:00 while waiting for the dashboard to be responsive. at Aspire.Hosting.Dcp.ApplicationExecutor.WaitForHttpSuccessOrThrow(Uri url, TimeSpan timeout, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 307 at Aspire.Hosting.Dcp.ApplicationExecutor.CheckDashboardAvailabilityAsync(String delimitedUrlList, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 263 at Aspire.Hosting.Dcp.ApplicationExecutor.StartDashboardAsDcpExecutableAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 239 at Aspire.Hosting.Dcp.ApplicationExecutor.RunApplicationAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 92 at Aspire.Hosting.Dcp.DcpHostService.StartAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/DcpHostService.cs:line 65 at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token) at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func3 operation) at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token) at Aspire.Hosting.DistributedApplication.RunAsync(CancellationToken cancellationToken) in //src/Aspire.Hosting/DistributedApplication.cs:line 132 — End of inner exception stack trace — at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at System.Threading.Tasks.Task.Wait() at Aspire.Hosting.DistributedApplication.Run() in /_/src/Aspire.Hosting/DistributedApplication.cs:line 153 at Program.<Main>$(String[] args) in /Users/vs/lisa3/aspire1/aspire1.AppHost/Program.cs:line 3

EXPECTED No error and warning shows with run the project.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 32 (17 by maintainers)

Most upvoted comments

Just verified, I did not met your error with Aspire.projecttemplates.8.0.0-preview.3.24105.21 on Mac OS. image

Verified today, this issue is not repro on 8.0.0-preview.3.24081.11.

Update your eshop bits and you’ll have the new version that uses preview 5.

Migrated from preview 3 to preview 4. Updated Visual Studio, updated workload. Got same issue - Timed out after 00:01:00 while waiting for the dashboard to be responsive. Changing ports in launchsettings did not help.

I had the same issue in Windows, @mo3in your workaround helped. I had an issue with an empty Dashboard, and then I changed the applicationUrl in launchSettings.json, and got this timeout issue.

After creating a sample project I took its launchSettings.json and everything works fine. Here is the diff image

UPD: I have Aspire 8.0.0-preview.4.24156.9

UPD2: I have to do that daily. After some time my Dashboard starts empty, and only the creation of the new Aspire project and usage of its launch settings helps.

i replaced AppHost launchSettings.json with new project launchSetting, now its run and working!

It looks like we are properly marking Aspire.Dashboard as executable (in the sense that ls -l on the file shows the executable flag set), but we still didn’t end up with a valid executable file. Things DO work fine on Linux (I installed on WSL and the file has the executable flag set, plus I can run the Dashboard executable successfully). This is likely either a build or possibly a signing issue with the Mac binary, but either way it’s going to be more work to fix the executable for Mac than we likely want to do right now.

OK I figured this out. It seems like the dashboard isn’t an executable on MacOS:

image

Seems like we have a publishing/packaging issue here.

Thoughts @danegsta @drewnoakes?

cc @joperezr