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

[turborepo] regression on handling SIGINT #4677

Closed
notaphplover opened this issue Apr 22, 2023 · 1 comment
Closed

[turborepo] regression on handling SIGINT #4677

notaphplover opened this issue Apr 22, 2023 · 1 comment
Labels
kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage

Comments

@notaphplover
Copy link

What version of Turborepo are you using?

1.9.3

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Linux

Describe the Bug

Turborepo seems not to correctly handle signal traps. It seems to exit processes on unexpected codes in some cases.

This is exactly #3711. @chris-olszewski closed the issue as resolved but the bug persists. After having requested to reopen the issue 10 days ago, I am subitting the issue again in order to track it until is solved.

I'm tagging the old participants so they can track this issue: @zanona @mehulkar @gajus

Expected Behavior

Turborepo should correctlyl handle signal traps.

To Reproduce

I uploaded a reproduction repo in case it's helpful. Additional instructions are added in the README file.

Reproduction Repo

https://github.com/notaphplover/turborepo-trap-issue

@notaphplover notaphplover added area: turborepo kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels Apr 22, 2023
@tknickman
Copy link
Member

Hey @notaphplover, thanks for the new issue - we've re-opened #3711, so I'm going to close this one to ensure there's a single issue for this bug!

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 needs: triage New issues get this label. Remove it after triage
Projects
None yet
Development

No branches or pull requests

2 participants