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

Dev Scripts: Leftover Node.js Processes After Removing Nuxt #5630

Closed
Tracked by #4580
rak-phillip opened this issue Oct 2, 2023 · 0 comments · Fixed by #5631
Closed
Tracked by #4580

Dev Scripts: Leftover Node.js Processes After Removing Nuxt #5630

rak-phillip opened this issue Oct 2, 2023 · 0 comments · Fixed by #5631
Assignees
Labels
kind/bug Something isn't working kind/quality quality improvements, refactoring, Automation via CI, E2E, Integration, CLI or REST API
Milestone

Comments

@rak-phillip
Copy link
Contributor

rak-phillip commented Oct 2, 2023

After removing Nuxt from Rancher Desktop, we are encountering an issue where multiple Node.js processes are left after exiting a development build. This behavior is related to Vue CLI spawning child processes that are not properly tracked and terminated by the development script.

Expected Behavior

When running a development build, we expect all Node.js processes to be cleanly terminated once the build is completed.

Steps to Reproduce

  1. Run a development build
  2. Exit Rancher Desktop via File => Exit
  3. Check for leftover Node.js processes using pslist | select-string "node"

Actual Behavior:

After running a development build, we observe that multiple Node.js processes are still active.

@rak-phillip rak-phillip changed the title Dev scripts: kill all renderer process Dev Scripts: Leftover Node.js Processes After Removing Nuxt Oct 2, 2023
@rak-phillip rak-phillip self-assigned this Oct 2, 2023
@rak-phillip rak-phillip added kind/bug Something isn't working kind/quality quality improvements, refactoring, Automation via CI, E2E, Integration, CLI or REST API labels Oct 2, 2023
@rak-phillip rak-phillip added this to the 1.11 milestone Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working kind/quality quality improvements, refactoring, Automation via CI, E2E, Integration, CLI or REST API
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant