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

chore: tests in example-remix-app leaves a hanging esbuild process #397

Closed
threepointone opened this issue Feb 6, 2022 · 1 comment · Fixed by #670, #678 or #679
Closed

chore: tests in example-remix-app leaves a hanging esbuild process #397

threepointone opened this issue Feb 6, 2022 · 1 comment · Fixed by #670, #678 or #679
Assignees
Labels
maintenance Maintenance task pages Relating to Pages

Comments

@threepointone
Copy link
Contributor

On my machine, running npm test occasionally leaves a hanging esbuild process (say, 1 out of 3 times). Looking closer, it appears to be coming from example-remix-app, which means running jest --forceExit isn't cleanly shutting it down. We should fix this.
image

@threepointone
Copy link
Contributor Author

This is still happening :(

threepointone added a commit that referenced this issue Mar 23, 2022
We weren't killing the process started by wrangler whenever its parent was killed. This fix is to listen on SIGTERM/SIGTERM and kill that process. This also lets us remove `--forceExit` from the test runner calls. I also did some minor configuration cleanups.

Fixes #397 and #618
threepointone added a commit that referenced this issue Mar 23, 2022
We weren't killing the process started by wrangler whenever its parent was killed. This fix is to listen on SIGINT/SIGTERM and kill that process. This also lets us remove `--forceExit` from the test runner calls. I also did some minor configuration cleanups.

Fixes #397 and #618
threepointone added a commit that referenced this issue Mar 23, 2022
We weren't killing the process started by wrangler whenever its parent was killed. This fix is to listen on SIGINT/SIGTERM and kill that process. This also lets us remove `--forceExit` from the test runner calls. I also did some minor configuration cleanups.

Fixes #397 and #618
threepointone added a commit that referenced this issue Mar 23, 2022
We weren't killing the process started by wrangler whenever its parent was killed. This fix is to listen on SIGINT/SIGTERM and kill that process. I also did some minor configuration cleanups.

Fixes #397 and #618
threepointone added a commit that referenced this issue Mar 23, 2022
We weren't killing the process started by wrangler whenever its parent was killed. This fix is to listen on SIGINT/SIGTERM and kill that process. I also did some minor configuration cleanups.

Fixes #397 and #618
threepointone added a commit that referenced this issue Mar 23, 2022
We weren't killing the process started by wrangler whenever its parent was killed. This fix is to listen on SIGINT/SIGTERM and kill that process. I also did some minor configuration cleanups.

Fixes #397
Fixes #618
mrbbot added a commit that referenced this issue Oct 31, 2023
This is required to use compatibility flags without a default-on
date, e.g. `streams_enable_constructors`
mrbbot added a commit that referenced this issue Nov 1, 2023
This is required to use compatibility flags without a default-on
date, e.g. `streams_enable_constructors`
mrbbot added a commit that referenced this issue Nov 1, 2023
This is required to use compatibility flags without a default-on
date, e.g. `streams_enable_constructors`
mrbbot added a commit that referenced this issue Nov 1, 2023
This is required to use compatibility flags without a default-on
date, e.g. `streams_enable_constructors`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment