Skip to content
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][Aspire] When we click 'Stop' or 'Restart' button in Aspire dashboard after dotnet watch for Aspire Starter App, there is an error "[AspireStarterApp.XXX (net9.0)] Exited with error code -1". #7204

Open
Rita003 opened this issue Jan 22, 2025 · 4 comments
Labels
area-tooling untriaged New issue has not been triaged

Comments

@Rita003
Copy link

Rita003 commented Jan 22, 2025

REGRESSION INFO: Work in SDK 9.0.102 + Aspire 9.0.0/9.1P1

INSTALL STEPS

  1. Clean machine: Windows x64
  2. Install SDK 9.0.200
  3. Install Aspire 9.0.0

REPRO STEPS

  1. Open CMD, create an Aspire Starter App using following commands:
dotnet new aspire-starter -o AspireStarterApp
cd AspireStarterApp
  1. Dotnet watch the project in CMD.
    dotnet watch
  2. Click the 'Stop' or 'Restart' button any project under "Actions"

Note

  1. This issue also repro after installing the latest SDK 9.0.200 + Aspire 9.1.0-preview.1.25071.1

ACTUAL
There is an error in CLI
Image

Error Log

dotnet watch ❌ [Aspire9StarterApp03.ApiService (net9.0)] Exited with error code -1
dotnet watch ❌ [Aspire9StarterApp03.Web (net9.0)] Exited with error code -1
@davidfowl
Copy link
Member

davidfowl commented Jan 22, 2025

cc @tmat did we regress stop/start/restart

@tmat
Copy link
Member

tmat commented Jan 22, 2025

This is currently expected. The only "graceful" process kill is triggered by user pressing Ctrl+C.

@davidfowl
Copy link
Member

Ah yes we know this 😄 . This is on windows only right? We send signals on the other operating systems yes?

@tmat
Copy link
Member

tmat commented Jan 22, 2025

Yes. Although, I think on Linux exit code for SIG_TERM is 143 or something like that.

@joperezr joperezr added untriaged New issue has not been triaged area-tooling labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-tooling untriaged New issue has not been triaged
Projects
None yet
Development

No branches or pull requests

4 participants