[WebToolsE2E] [Aspire] An unhandled exception was thrown after clicking the Stop and Start icons in the 'webfrontend' project on the Aspire dashboard.

[ymmendoza]

REGRESSION INFO:

1. Worked in Aspire 8.2.2/9.0.1

INSTALL STEPS

1. Clean machine: Win11 x64 23h2 ENU
2. Install SDK 9.0.102
3. Install Aspire 9.1.0-preview.1.25104.6
   Apply dotnet9 feed

REPRO STEPS:

1. Open CMD, create an Aspire Starter App using following commands:

dotnet new aspire-starter --use-redis-cache -o AspireApp1
cd AspireApp1
cd AspireApp1.AppHost

2. Dotnet run the project in CMD, and open URL in the browser.

dotnet build
Dotnet run

3. Click the stop button of "cache" and "webfrontend" then click the start button of webfrontend.

ACTUAL
After clicking the start button of 'webfrontend' and the notification error will pop up with an error in CMD.

Error Message:

      Failed to start resource webfrontend
      Aspire.Hosting.DistributedApplicationException: Resource 'cache' has entered the 'Exited' state prematurely.
         at Aspire.Hosting.ApplicationModel.ResourceNotificationService.<>c__DisplayClass14_0.<<WaitUntilHealthyAsync>g__Core|1>d.MoveNext() in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 170
      --- End of stack trace from previous location ---
         at Aspire.Hosting.ApplicationModel.ResourceNotificationService.WaitUntilHealthyAsync(IResource resource, IResource dependency, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 146
         at Aspire.Hosting.ApplicationModel.ResourceNotificationService.WaitForDependenciesAsync(IResource resource, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 308
         at Aspire.Hosting.Orchestrator.ApplicationOrchestrator.WaitForInBeforeResourceStartedEvent(BeforeResourceStartedEvent event, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Orchestrator/ApplicationOrchestrator.cs:line 76
         at Aspire.Hosting.Eventing.DistributedApplicationEventing.<>c__DisplayClass4_0`1.<<Subscribe>b__0>d.MoveNext() in /_/src/Aspire.Hosting/Eventing/DistributedApplicationEventing.cs:line 82
      --- End of stack trace from previous location ---
         at Aspire.Hosting.Eventing.DistributedApplicationEventing.PublishAsync[T](T event, EventDispatchBehavior dispatchBehavior, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Eventing/DistributedApplicationEventing.cs:line 69
         at Aspire.Hosting.Orchestrator.ApplicationOrchestrator.OnResourceStarting(OnResourceStartingContext context) in /_/src/Aspire.Hosting/Orchestrator/ApplicationOrchestrator.cs:line 133
         at Aspire.Hosting.Dcp.DcpExecutorEvents.PublishAsync[T](T context) in /_/src/Aspire.Hosting/Dcp/DcpExecutorEvents.cs:line 33
         at Aspire.Hosting.Dcp.DcpExecutor.<>c__DisplayClass74_0.<<StartResourceAsync>g__StartExecutableOrContainerAsync|0>d`1.MoveNext() in /_/src/Aspire.Hosting/Dcp/DcpExecutor.cs:line 1595
      --- End of stack trace from previous location ---
         at Aspire.Hosting.Dcp.DcpExecutor.StartResourceAsync(IResourceReference resourceReference, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/DcpExecutor.cs:line 1538

EXPECTED
No notification errors displayed when starting the project.

[davidfowl]

@JamesNK can you look at this one.

[JamesNK]

Isn't it this: #7186

Your WaitForBehavior PR is already addressing it.

[danmoseley]

closing as dupe as it seems so

[ymmendoza]

I verified this issue on Aspire 9.1.0-preview.1.25111.2. I can no longer reproduce it.