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.

Sign up for GitHub

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

Jump to bottom

The Node process stays active after resolve applications are stopped. #2126

Closed
Matosov opened this issue Nov 15, 2021 · 0 comments · Fixed by #2127
Closed

The Node process stays active after resolve applications are stopped. #2126

Matosov opened this issue Nov 15, 2021 · 0 comments · Fixed by #2127
Assignees
@FreeSlave
Labels
bug Issues related to defects and incorrect/unexpected feature behavior severity: major Issues with high impact on the product, e.g., new packages, installation issues, etc.

Comments

@Matosov
Copy link

Matosov commented Nov 15, 2021

  1. Execute the following command in order to create a new resolve application:
    npx create-resolve-app resolve-shopping-list-redux -e shopping-list-redux

  2. Change current folder to the just created:
    cd resolve-shopping-list-redux

  3. Run the application:
    yarn dev

There are 4 Node processes in the processes list (picture 1).

  1. Press the Ctrl+C keys within the terminal where the application was started in order to stop it.

There are 1 Node process in the processes list now (picture 2).

  1. Run the application again.
    yarn dev

An error is in the terminal log (picture 3). Though the application is started.

Node version: 14.17.6
Yarn version: 1.22.5
MacOS version: 12.0.1

1

2

3
@Matosov Matosov added the bug Issues related to defects and incorrect/unexpected feature behavior label Nov 15, 2021
@MrCheater MrCheater added the severity: major Issues with high impact on the product, e.g., new packages, installation issues, etc. label Nov 16, 2021
FreeSlave added a commit that referenced this issue Nov 16, 2021
@FreeSlave
Exit process from signal handler. Possible fix for #2126
d4e000a
@MrCheater MrCheater linked a pull request Nov 16, 2021 that will close this issue
Exit process from signal handler. Possible fix for #2126 #2127
Merged
FreeSlave added a commit that referenced this issue Nov 16, 2021
@FreeSlave
Exit process from signal handler. Possible fix for #2126 (#2127)
60b3454
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FreeSlave FreeSlave

Labels
bug Issues related to defects and incorrect/unexpected feature behavior severity: major Issues with high impact on the product, e.g., new packages, installation issues, etc.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Exit process from signal handler. Possible fix for #2126 reimagined/resolve
3 participants
@MrCheater @FreeSlave @Matosov