-
Notifications
You must be signed in to change notification settings - Fork 734
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
fix: cleanup after pages dev
tests
#678
Conversation
🦋 Changeset detectedLatest commit: 2549799 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
2f70d9c
to
a8193b8
Compare
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2027536893/npm-package-wrangler-678 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/678/npm-package-wrangler-678 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/2027536893/npm-package-wrangler-678 dev path/to/script.js |
a8193b8
to
78e11ef
Compare
console.log(chunk.toString()); | ||
}); | ||
}); | ||
|
||
afterAll(() => { | ||
wranglerProcess.kill(); | ||
afterAll(async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could probably clean this up by using execa here, but I'll leave that for some other time/person
oh lol this hangs on windows and ubuntu huh |
78e11ef
to
a3d2c35
Compare
pages dev
testspages dev
tests
a3d2c35
to
5cad8f3
Compare
pages dev
testspages dev
tests
Aight, looks like forceExit is still necessary for windows/ubuntu. |
c2f0c6c
to
1ee1c91
Compare
1ee1c91
to
2549799
Compare
@@ -27,6 +27,7 @@ const EXIT = (message?: string, code?: number) => { | |||
if (message) console.log(message); | |||
if (code) process.exitCode = code; | |||
EXIT_CALLBACKS.forEach((callback) => callback()); | |||
RUNNING_BUILDERS.forEach((builder) => builder.stop?.()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This cleans up hanging esbuild processes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, thought we'd got it yesterday! Let's see if this does it now.
🤞 |
With #656, the Queues dispatcher is now implemented as part of the broker Durable Object. We no longer send message batches directly from Node.js, so can remove queue handling from the entry worker. Note the magic proxy enqueues messages through queue producer bindings like regular workers, so never used this endpoint directly.
With #656, the Queues dispatcher is now implemented as part of the broker Durable Object. We no longer send message batches directly from Node.js, so can remove queue handling from the entry worker. Note the magic proxy enqueues messages through queue producer bindings like regular workers, so never used this endpoint directly.
With #656, the Queues dispatcher is now implemented as part of the broker Durable Object. We no longer send message batches directly from Node.js, so can remove queue handling from the entry worker. Note the magic proxy enqueues messages through queue producer bindings like regular workers, so never used this endpoint directly.
With #656, the Queues dispatcher is now implemented as part of the broker Durable Object. We no longer send message batches directly from Node.js, so can remove queue handling from the entry worker. Note the magic proxy enqueues messages through queue producer bindings like regular workers, so never used this endpoint directly.
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
(fyi this does NOT cleanup the occasional flake with the remix test where the text doesn't render)