Skip to content

Make IInteractionService unavailable during BeforeStart to prevent deadlock - #21553

Merged
David Fowler (davidfowl) merged 6 commits into
mainfrom
davidfowl/fix-interaction-beforestart-11371
Nov 1, 2026
Merged

David Fowler (davidfowl) merged 6 commits into
mainfrom
davidfowl/fix-interaction-beforestart-11371

Conversation

@davidfowl

@davidfowl David Fowler (davidfowl) commented Oct 31, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Fixes #11371

Using IInteractionService from a BeforeStartEvent subscriber deadlocked the app host, even when the prompt was guarded by interactionService.IsAvailable.

Root cause

DistributedApplication.ExecuteBeforeStartHooksAsync (BeforeStartEvent subscribers, IDistributedApplicationLifecycleHook.BeforeStartAsync, and the before-start pipeline step) runs before _host.StartAsync. Interactions are answered only by the dashboard (started by the orchestrator hosted service) and the CLI backchannel (BackchannelService), and both are hosted services. So during before-start nothing can respond to an interaction. However, InteractionService.IsAvailable only checked DisableDashboard, the non-interactive CLI scope, and the interactivity config, so it returned true. An awaited prompt was added to the interaction collection and waited on a TaskCompletionSource that could never complete, which blocked host startup.

Fix

  • IInteractionService gets an internal MarkConsumersReady(bool ready) member with a default no-op body, so the public API is unchanged. DistributedApplication's constructor calls MarkConsumersReady(false), and from then on IsAvailable returns false. This also covers code that prompts after Build() but before Run() reaches the hooks. A standalone InteractionService that isn't hosted by a DistributedApplication is unaffected.
  • ExecuteBeforeStartHooksAsync calls MarkConsumersReady(true) in a finally block after events, lifecycle hooks and before-start pipeline steps have run. This happens before _host.StartAsync, so hosted services (DCP host, parameter processing, pipeline executor, version check) see the same availability as before. There's no cast to InteractionService. The design was reshaped (ref-counted scope → one-way flag → MarkConsumersReady(bool)) after review feedback from JamesNK.
  • Because prompt methods already call EnsureServiceAvailable(), unguarded prompts during before-start now throw InvalidOperationException right away instead of hanging. The exception message now mentions this case. The IsAvailable XML docs gain a <remarks> explaining it.

I used an instance-level flag instead of the existing AsyncLocal non-interactive scope on purpose. An AsyncLocal would flow into background tasks started from before-start handlers and keep them non-interactive permanently, even after the dashboard is up. With the flag, availability goes back to true as soon as before-start completes.

Before (main): real apphost, BeforeStartEvent prompt guarded by IsAvailable

The process was killed by timeout 60, with exit code 124. The host never started, no dashboard came up, and no resources were created:

[repro] BeforeStartEvent: IsAvailable=True
[repro] Awaiting PromptMessageBoxAsync...
EXIT=124 (124 = killed by 60s timeout)

After (this PR): same apphost

[repro] BeforeStartEvent: IsAvailable=False
[repro] Interaction service unavailable during BeforeStart; skipping prompt.
info: Aspire.Hosting.DistributedApplication[0]
      Distributed application starting.
info: Aspire.Hosting.Dcp.DcpHost[0]
      Starting DCP with arguments: start-apiserver ...
[repro] AfterResourcesCreatedEvent fired: app host started successfully.
info: Aspire.Hosting.DistributedApplication[0]
      Distributed application started. Press Ctrl+C to shut down.
info: Aspire.Hosting.DistributedApplication[0]
      Now listening on: http://localhost:15999
      Aspire Dashboard
            - Dashboard:  http://localhost:15999

curl http://localhost:15999/ returned 302, so the dashboard was serving. Both runs used a scratch apphost on Linux, built from this repo (main vs. this branch), with one executable resource and the exact handler from the issue. The scratch apphost is not committed.

Tests

New tests in tests/Aspire.Hosting.Tests/InteractionServiceTests.cs:

  • BeforeStartEvent_PromptIsGuardedByIsAvailable_DoesNotDeadlock: builds a real app with the dashboard enabled, subscribes to BeforeStartEvent, records IsAvailable and awaits PromptMessageBoxAsync, checks that IsAvailable is false and prompts fail fast right after Build(), then runs ExecuteBeforeStartHooksAsync. It asserts that IsAvailable was false during the event, that the prompt threw InvalidOperationException instead of hanging, and that IsAvailable is true again afterwards.
    • Without the fix, with the DistributedApplication wiring reverted, it fails: System.TimeoutException : The operation at InteractionServiceTests.cs:238 timed out after reaching the limit of 5000ms.
    • With the fix, it passes.
  • IsAvailable_ConsumersNotReady_ReturnsFalseAndPromptsThrow: unit coverage of the flag. It checks that IsAvailable is false after MarkConsumersReady(false), that the prompt throws early with a message naming BeforeStartEvent, that no interaction is queued, and that availability is restored after MarkConsumersReady(true).

Local run with the fix, covering InteractionServiceTests, ParameterProcessorTests, DistributedApplicationPipelineTests, PipelineExecutorTests, ResourceCommandServiceTests, VersionCheckServiceTests, ComputeEnvironmentValidationTests, ContainerRuntimeReadinessTests and RequiredCommandAnnotationTests: 374 of 375 passed. The one failure, ParameterProcessorTests.DeleteParameterCoreAsync_AddsParameterBackToUnresolvedAndStartsResolutionTask, is a pre-existing intermittent failure. It uses a TestInteractionService and doesn't touch the changed code. When rerun alone it failed 1 of 5 times. InteractionServiceTests passed 80 of 80.

Playground

playground/Stress/Stress.AppHost already hosts the interaction samples. It now has a BeforeStartEvent subscriber that uses the issue's IsAvailable guard and prompt pattern. With the fix, the Stress apphost gets past before-start into DCP orchestration. In my sandbox, the Stress app later failed on an unrelated, environment-specific coordinated build of its child .NET projects, so I used the scratch apphost above for the clean E2E evidence.

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
    • No

🤖 Posted by AspireAgent (AI Agent)

Interactions are answered by the dashboard and CLI backchannel, which are
hosted services that only start after BeforeStartEvent, lifecycle hooks and
the before-start pipeline step complete. IsAvailable returned true during
that window, so awaiting a prompt guarded by IsAvailable deadlocked the app
host. IsAvailable now returns false while before-start hooks run, and
prompts throw early instead of waiting forever.

Fixes #11371

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 21553

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 21553"

@github-actions github-actions Bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Oct 31, 2026
@aspire-repo-bot
aspire-repo-bot Bot requested a balanced review from Copilot October 31, 2026 08:27
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues remain for the change intended to prevent before-start interaction prompts from blocking AppHost startup.

No open issues 🎉

What changed in this PR

Prevents the AppHost startup deadlock described in #11371 by making IInteractionService unavailable while before-start hooks run. Guarded prompts can skip interaction, while unguarded prompts fail immediately instead of blocking startup.

Changes:

  • Adds a reference-counted, idempotent scope that disables interactions during before-start execution and restores availability afterward.
  • Updates availability documentation and the exception message.
  • Adds regression tests and a guarded-prompt example in the Stress playground.
File Description
tests/​Aspire.Hosting.Tests/​InteractionServiceTests.cs Tests prompt rejection, availability restoration, double disposal, and before-start integration.
src/​Aspire.Hosting/​InteractionService.cs Implements the before-start scope and updates the unavailable-service error.
src/​Aspire.Hosting/​IInteractionService.cs Documents interaction unavailability during before-start hooks.
src/​Aspire.Hosting/​DistributedApplication.cs Holds the interaction scope throughout before-start execution.
playground/​Stress/​Stress.AppHost/​AppHost.cs Demonstrates guarding a before-start prompt with IsAvailable.

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

Copy link
Copy Markdown
Collaborator Author

CI failures on attempt 1 are known flakes unrelated to this change. The repo's transient-failure automation reran the failed jobs once (attempt 2):

  • Hosting.MongoDB (ubuntu-latest): MongoDbReplicaSetFunctionalTests (VerifyReplicaSetInitializesWhenAMemberNeverBecomesHealthy, VerifyMongoDBMultiNodeReplicaWithDataShouldWorkAcrossUsages). This is the known replica-set flake, [CI Failure] Flaky: MongoDbReplicaSetFunctionalTests.VerifyMongoDBMultiNodeReplicaWithDataShouldWorkAcrossUsages fails to become healthy #20478.
  • Hosting.DevTunnels (windows-latest) and Hosting.DotnetTool (windows-latest): "The hosted runner lost communication with the server" (Windows runner loss). Both projects passed on ubuntu-latest in the same run. Neither one exercises the changed code path: DotnetTool tests don't use interactions, and DevTunnels tests register TestInteractionService, so the new before-start scope doesn't apply to them.

🤖 Posted by AspireAgent (AI Agent)

David Fowler (davidfowl) commented Oct 31, 2026 •

Copy link
Copy Markdown
Collaborator Author

CI on head ea20fcae after the single rerun (attempt 2):

  • 333 checks pass, including Hosting.DevTunnels (windows-latest) on the rerun, and 13 are skipped.
  • Hosting.MongoDB (ubuntu-latest) failed again with the known flake [CI Failure] Flaky: MongoDbReplicaSetFunctionalTests.VerifyMongoDBMultiNodeReplicaWithDataShouldWorkAcrossUsages fails to become healthy #20478: MongoDbReplicaSetFunctionalTests.VerifyMongoDBMultiNodeReplicaWithDataShouldWorkAcrossUsages(topologyChange: MemberPrepended), "Stopped waiting for resource 'rs0' to become healthy". The Mongo tests don't exercise InteractionService or the before-start path.
  • Hosting.DotnetTool (windows-latest) is hung again in "Run tests (Windows)". On attempt 1 the runner lost communication. Another open PR currently shows the same Windows DotnetTool hang, and the DotnetTool tests don't use interactions.

Its one rerun is used up, so I'm leaving this PR as a draft. A maintainer can decide whether to rerun these flakes or merge with them failing.

🤖 Posted by AspireAgent (AI Agent)

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

Copy link
Copy Markdown
Collaborator Author

CI on head ea20fcae is now fully green: 337 checks pass and 14 are skipped.

The repo's retry automation reran only the failed jobs once more (attempt 3 of the CI run). Both jobs passed:

Neither flake touches InteractionService or the before-start path. There's no open review feedback, so I'm marking this PR ready for review.

🤖 Posted by AspireAgent (AI Agent)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One design question about interaction-service startup readiness.

Reshape the before-start guard into a one-way flag per review feedback:
DistributedApplication marks the interaction service as pending when it's
created and completes it once ExecuteBeforeStartHooksAsync finishes. This
also covers code that prompts after Build() but before Run() reaches the
before-start hooks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are recorded for the startup interaction-availability change.

No open issues 🎉

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

Address review feedback: InteractionService now starts not ready by default and
the app host calls IInteractionService.MarkConsumersReady() (internal default
interface member) after before-start hooks complete, instead of casting to
InteractionService and marking hooks pending in the constructor.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aspire-repo-bot
aspire-repo-bot Bot requested a balanced review from Copilot October 31, 2026 14:58
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues were identified for the startup interaction-readiness change.

No open issues 🎉

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

Address review feedback: undo the not-ready-by-default change from ac04b8a and
replace the pending/complete pair with a single internal
IInteractionService.MarkConsumersReady(bool ready). DistributedApplication marks
consumers not ready when created and ready after before-start hooks, without
casting to InteractionService.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues remain for the startup interaction-availability changes.

No open issues 🎉

Review effort: Balanced

Copy link
Copy Markdown
Collaborator Author

CI note for head 594ef29: the Native hosting validation job ("Native AOT, generated SDK, Docker, DCP, CLI and Dashboard") was cancelled after reaching its 35-minute limit. It got stuck in workload-dashboard-smoke, where the dashboard repeatedly logged Connection refused to the native resource service (log grew to 2.9k lines; the passing run's log is 161 lines).

I think this is unrelated to this PR:

  • The native server and core projects don't reference Aspire.Hosting, which is the only place this change touches.
  • The same job passed on the previous heads ac04b8a, 5788e17 and ea20fca.

I've rerun the failed job once.

Hosting.MongoDB (ubuntu) also failed, which is known flake #20478. I'm leaving that one to the retry automation.

🤖 Posted by AspireAgent (AI Agent)

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

A testing wrapper can reset readiness after before-start hooks have completed without rerunning them, leaving dashboard-enabled testing apps permanently non-interactive; initialization must be limited to the original build and covered by a regression test.

1 open issue

Review effort: Balanced

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The supplied review evidence identifies no active issues requiring changes.

No open issues 🎉

1 resolved since last review

Review effort: Balanced

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Tests selector

52 / 100 PR test projects · 4 PR jobs, from 15 changed files.

Selected PR test projects (52 / 100)

Aspire.Cli.EndToEnd.Tests, Aspire.Hosting.Analyzers.Tests, Aspire.Hosting.Azure.EntraId.Tests, Aspire.Hosting.Azure.Kubernetes.Tests, Aspire.Hosting.Azure.Kusto.Tests, Aspire.Hosting.Azure.Provisioning.Tests, Aspire.Hosting.Azure.Tests, Aspire.Hosting.Blazor.Tests, Aspire.Hosting.Browsers.Tests, Aspire.Hosting.CodeGeneration.Go.Tests, Aspire.Hosting.CodeGeneration.Java.Tests, Aspire.Hosting.CodeGeneration.Python.Tests, Aspire.Hosting.CodeGeneration.Rust.Tests, Aspire.Hosting.CodeGeneration.TypeScript.Tests, Aspire.Hosting.Containers.Tests, Aspire.Hosting.DevTunnels.Tests, Aspire.Hosting.Docker.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Hosting.DotnetTool.Tests, Aspire.Hosting.EntityFrameworkCore.Tests, Aspire.Hosting.Foundry.Tests, Aspire.Hosting.Garnet.Tests, Aspire.Hosting.Go.Tests, Aspire.Hosting.Java.Tests, Aspire.Hosting.JavaScript.Tests, Aspire.Hosting.Kafka.Tests, Aspire.Hosting.Keycloak.Tests, Aspire.Hosting.Kubernetes.Tests, Aspire.Hosting.Maui.Tests, Aspire.Hosting.Milvus.Tests, Aspire.Hosting.MongoDB.Tests, Aspire.Hosting.MySql.Tests, Aspire.Hosting.Nats.Tests, Aspire.Hosting.OpenAI.Tests, Aspire.Hosting.Oracle.Tests, Aspire.Hosting.Orleans.Tests, Aspire.Hosting.PostgreSQL.Tests, Aspire.Hosting.Python.Tests, Aspire.Hosting.Qdrant.Tests, Aspire.Hosting.RabbitMQ.Tests, Aspire.Hosting.Radius.Tests, Aspire.Hosting.Redis.Tests, Aspire.Hosting.RemoteHost.Tests, Aspire.Hosting.Rust.Tests, Aspire.Hosting.Seq.Tests, Aspire.Hosting.SqlServer.Tests, Aspire.Hosting.Testing.Tests, Aspire.Hosting.Tests, Aspire.Hosting.Valkey.Tests, Aspire.Hosting.Yarp.Tests, Aspire.Playground.Tests, Aspire.Templates.Tests

Selected PR jobs (4)

cli-starter-validation, extension-e2e, polyglot, typescript-api-compat


How these were chosen — grouped by what changed

⚠️ 45 of the 52 selected test projects come from a single change — src/Aspire.Hosting/DistributedApplication.cs.

🔧 src/Aspire.Hosting/DistributedApplication.cs (changed source)
→ 45 via the project graph

show 45

Aspire.Hosting.Analyzers.Tests (2 hops), Aspire.Hosting.Azure.EntraId.Tests (2 hops), Aspire.Hosting.Azure.Kubernetes.Tests (2 hops), Aspire.Hosting.Azure.Kusto.Tests (2 hops), Aspire.Hosting.Azure.Provisioning.Tests (3 hops), Aspire.Hosting.Azure.Tests, Aspire.Hosting.Browsers.Tests (2 hops), Aspire.Hosting.CodeGeneration.Go.Tests, Aspire.Hosting.CodeGeneration.Java.Tests, Aspire.Hosting.CodeGeneration.Python.Tests, Aspire.Hosting.CodeGeneration.Rust.Tests, Aspire.Hosting.CodeGeneration.TypeScript.Tests, Aspire.Hosting.Containers.Tests (2 hops), Aspire.Hosting.DevTunnels.Tests (2 hops), Aspire.Hosting.Docker.Tests (2 hops), Aspire.Hosting.DotnetTool.Tests (2 hops), Aspire.Hosting.EntityFrameworkCore.Tests (2 hops), Aspire.Hosting.Foundry.Tests (2 hops), Aspire.Hosting.Garnet.Tests (2 hops), Aspire.Hosting.Go.Tests (2 hops), Aspire.Hosting.Java.Tests (2 hops), Aspire.Hosting.JavaScript.Tests (2 hops), Aspire.Hosting.Kafka.Tests (2 hops), Aspire.Hosting.Keycloak.Tests (2 hops), Aspire.Hosting.Kubernetes.Tests (2 hops), Aspire.Hosting.Maui.Tests, Aspire.Hosting.Milvus.Tests (2 hops), Aspire.Hosting.MongoDB.Tests (2 hops), Aspire.Hosting.MySql.Tests (2 hops), Aspire.Hosting.Nats.Tests (2 hops), Aspire.Hosting.OpenAI.Tests (2 hops), Aspire.Hosting.Oracle.Tests (2 hops), Aspire.Hosting.Orleans.Tests (2 hops), Aspire.Hosting.PostgreSQL.Tests (2 hops), Aspire.Hosting.Python.Tests (2 hops), Aspire.Hosting.Qdrant.Tests (2 hops), Aspire.Hosting.RabbitMQ.Tests (2 hops), Aspire.Hosting.Redis.Tests (2 hops), Aspire.Hosting.RemoteHost.Tests, Aspire.Hosting.Rust.Tests (2 hops), Aspire.Hosting.Seq.Tests (2 hops), Aspire.Hosting.SqlServer.Tests (2 hops), Aspire.Hosting.Valkey.Tests (2 hops), Aspire.Hosting.Yarp.Tests (2 hops), Aspire.Playground.Tests

🧪 tests/Aspire.Hosting.Tests/Dashboard/DashboardServiceDataTerminalTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests
→ 3 via the project graph: Aspire.Hosting.Blazor.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Hosting.Radius.Tests

📦 affected project Aspire.Hosting.Dotnet
→ 2 tests: Aspire.Cli.EndToEnd.Tests, Aspire.Templates.Tests

📦 affected project Aspire.Hosting
→ 1 test: Aspire.Cli.EndToEnd.Tests

📄 playground/Stress/Stress.AppHost/AppHost.cs (changed)
→ 1 directly: Aspire.Playground.Tests

🧪 tests/Aspire.Hosting.Testing.Tests/DashboardTestingBuilderTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Testing.Tests

🧪 tests/Aspire.Hosting.Tests/Dashboard/DashboardServiceTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

🧪 tests/Aspire.Hosting.Tests/InteractionServiceTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

🧪 tests/Aspire.Hosting.Tests/Orchestrator/ApplicationOrchestratorTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

🧪 tests/Aspire.Hosting.Tests/Orchestrator/ParameterProcessorTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

🧪 tests/Aspire.Hosting.Tests/Publishing/PipelineActivityReporterTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

🧪 tests/Aspire.Hosting.Tests/ResourceCommandServiceTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

🧪 tests/Aspire.Hosting.Tests/Terminals/InteractionServiceTerminalTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests

Job reasons

Job Triggered by
cli-starter-validation affected project Aspire.Hosting.JavaScript
extension-e2e • src/Aspire.Hosting/DistributedApplication.cs, src/Aspire.Hosting/DistributedApplicationBuilder.cs, src/Aspire.Hosting/IInteractionService.cs, src/Aspire.Hosting/InteractionService.cs, src/Aspire.Hosting/InteractionServiceConsumerState.cs
• affected project Aspire.Hosting
polyglot • affected project Aspire.Hosting
• affected project Aspire.Hosting.Azure.Provisioning.KeyVault
typescript-api-compat affected project Aspire.Hosting

Selection computed for commit 12fa2f0.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@davidfowl
David Fowler (davidfowl) merged commit 9a4024a into main Nov 1, 2026
690 of 693 checks passed
@microsoft-github-policy-service microsoft-github-policy-service Bot added this to the 17.0 milestone Nov 1, 2026
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Pull request created: #2022

Generated by PR Documentation Check · copilot · auto · 25.9 AIC · ⌖ 1.13 AIC · ⊞ 7.1K

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

📝 Documentation has been drafted in microsoft/aspire.dev#2022 targeting release/17.0.

No deterministic signals fired (docs_optional), but this is a user-visible behavior change to a documented feature: IInteractionService.IsAvailable now returns false during before-start and unguarded prompts throw InvalidOperationException. Added a caution Aside to extensibility/interaction-service.mdx.

Note

This draft PR needs human review before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using InteractionSerivce in BeforeStart deadlocks

3 participants