Cloudflare Developers•11mo ago

hello, kind of new in the game but it

hello, kind of new in the game but it seems since the last version of wrangler (or something else) that the workerd serve on my computer stays in a running state all the time. Is there a trick I don't know about. right now I need to kill it manually

4 Replies

Sébastien Morel•11mo ago

Ctrl-C or x does not change anything it stays on:

.../node_modules/.pnpm/@[email protected]/node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd serve --binary --experimental --socket-addr=entry=localhost:4242 --external-addr=loopback=localhost:57867 --control-fd=3 -

.../node_modules/.pnpm/@[email protected]/node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd serve --binary --experimental --socket-addr=entry=localhost:4242 --external-addr=loopback=localhost:57867 --control-fd=3 -

Adam•11mo ago

It looks like this is a bug with a recent version of wrangler/workerd: https://github.com/cloudflare/workers-sdk/issues/4612 We are working to resolve it.

GitHub

🐛 BUG: workerd inspector process doesn't die · Issue #4612 · cloudf...

Which Cloudflare product(s) does this pertain to? Workers Runtime What version(s) of the tool(s) are you using? 3.21.0 What version of Node are you using? 18.17.1 What operating system are you usin...

Kodie Goodwin•11mo ago

Cool, keeping an eye on this issue happening to me too

Sébastien Morel•11mo ago

ok @Adam thanks! thanks for the fix guys! @Adam if you have time to have a look in #workers-help I have a quick question about dns resolution inside a worker. Which seems to behave differently when reach on a custom domain versus worker.dev https://discord.com/channels/595317990191398933/1186554218224554014

Gaming

Programming

hello, kind of new in the game but it