You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting multiple wrangler dev processes in quick succession(via a tool like turbo or similar), the sessions can end up fighting over which of them gets to start the Registry. Others fail with the error
✘ [ERROR] failed to start worker registry Error: listen EADDRINUSE: address already in use 127.0.0.1:6284
Expected behavior
One of the Dev Sessions should complete, and any others should wait for it to become available before throwing an error.
Steps to reproduce
Create multiple Workers(doesn't matter their content). I did it with 5, but it should work with less/more too.
Start wrangler dev on them all simultaneously.
Credit to @poacher2k for discovering/reporting this bug on the CF Discord.
The text was updated successfully, but these errors were encountered:
The plan is to move to a file based registry in the shortish term. (There may be more significant approach to multi-worker development in the longer term). See #5214
I'll see if we can prioritise landing this before the end of the month.
Which Cloudflare product(s) does this pertain to?
Wrangler core
What version(s) of the tool(s) are you using?
3.60.3
What version of Node are you using?
22.2.0
What operating system and version are you using?
MacOS Sonoma 14.5
Describe the Bug
Observed behavior
When starting multiple
wrangler dev
processes in quick succession(via a tool liketurbo
or similar), the sessions can end up fighting over which of them gets to start the Registry. Others fail with the errorExpected behavior
One of the Dev Sessions should complete, and any others should wait for it to become available before throwing an error.
Steps to reproduce
wrangler dev
on them all simultaneously.Credit to @poacher2k for discovering/reporting this bug on the CF Discord.
The text was updated successfully, but these errors were encountered: