i'm not sure what has changed but it was working fine for me for quite awhile... now i can't either

D

DeepOP•6/24/24, 4:36 AM

{
"name": "Wrangler Dev Remote",
"type": "node",
"request": "launch",
"resolveSourceMapLocations": ["", "/node_modules/**"],
"program": "${workspaceFolder}/node_modules/wrangler/bin/wrangler.js",
"args": ["dev", "--inspector-port=59229", "--port=9999", "--remote"], //Force a high port to avoid conflicts with other debuggers
"attachSimplePort": 59229, //Matches --inspector-port above
"internalConsoleOptions": "neverOpen", // We want to see Wrangler's output usually so hide this
"console": "integratedTerminal", // Shows the wrangler output
"autoAttachChildProcesses": false
}

D

DeepOP•6/24/24, 4:37 AM

i'm trying to debug remotely as well. which, over the past several months, was working fine and was great... now...? maybe i'll try to install latest version of wrangler and see if that helps

D

DeepOP•6/24/24, 4:39 AM

Screenshot_2024-06-24_at_12.29.30_AM.png

D

DeepOP•6/24/24, 4:40 AM

this shows VSCode thinking it hit a breakpoint but in fact it didn't... i can't step, i can't inspect any variables and my postman request returns immediately with a response from my worker...

B

bnason•6/24/24, 1:05 PM

I'm trying to use

wrangler tail

wrangler tail

wrangler tail

wrangler tail to get my projects logs but I get the error

workers.api.error.script_not_found [code: 10007]

workers.api.error.script_not_found [code: 10007]

workers.api.error.script_not_found [code: 10007]

workers.api.error.script_not_found [code: 10007] My Nuxt app deployed fine and I am able to access it via the browser.

DDeep i'm not sure what has changed but it was working fine for me for quite awhile......

D

DeepOP•6/24/24, 1:33 PM

also... when I launch the remote dev configuration above wrangler will start to initialize, i can see my app controller starts and logs to console but then it immediately shuts down. so, honestly at this point, remote wrangler debugging is completely dead for me.... i've been using remote debugging for months and suddenly (past 2-3 weeks) it broke and isn't usable now. no clue why... hopefully someone at CF knows something...

B

bnason•6/24/24, 2:09 PM

So wrangler just made me go through the oauth process again, but now when I click Allow, wrangler throws an error.

SyntaxError: Unexpected token < in JSON at position 0

SyntaxError: Unexpected token < in JSON at position 0

SyntaxError: Unexpected token < in JSON at position 0

SyntaxError: Unexpected token < in JSON at position 0

D

DeepOP•6/24/24, 3:20 PM

ok, so here's what i've found in the wrangler logs that seem like it might be part of the issue...

--- 2024-06-24T15:16:57.498Z debug
workerd/util/symbolizer.c++:96: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use

--test_env=LLVM_SYMBOLIZER=<path>

--test_env=LLVM_SYMBOLIZER=<path>

--test_env=LLVM_SYMBOLIZER=<path>

--test_env=LLVM_SYMBOLIZER=<path>.
workerd/server/server.c++:3346: error: Uncaught exception: kj/compat/http.c++:2722: disconnected: worker_do_not_log; Request failed due to internal error
stack: 105a5edb0 106ec1420 105a60d90 105a60f4f 106ebcc1f 106ec1420 105a80138 1054158df 10513e5e8 10513e9f7 106ebcc1f 104fecf20 104aba5cf 105a8d26f 105a8e1d3 105a8eb93 105a565b8
workerd/server/server.c++:3346: error: Uncaught exception: kj/compat/http.c++:2722: disconnected: worker_do_not_log; Request failed due to internal error
stack: 105a5edb0 106ec1420 105a60d90 105a60f4f 106ebcc1f 106ec1420 105a80138 1054158df 10513e5e8 10513e9f7 106ebcc1f 104fecf20 104aba5cf 105a8d26f 105a8e1d3 105a8eb93 105a565b8

D

DeepOP•6/24/24, 3:22 PM

and not only that, the first errors i found in the wrangler logs was this one which i resolved/eliminated the error in the logs by creating dummy .env and .dev.vars files in my project...

--- 2024-06-24T15:14:44.307Z debug
Failed to load .env file "/Users/PROJECT_NAME/.dev.vars": Error: ENOENT: no such file or directory, open '/Users/PROJECT_NAME/.dev.vars'

D

DeepOP•6/24/24, 3:23 PM

anyway, i don't have time to debug this mess... i'm dropping remote debugging and working around the problem

D

DeepOP•6/24/24, 4:09 PM

well nevermind, i thought i could workaround this problem by doing local debugging... nope. no breakpoints get hit.... hopefully someone has a clue, i've exhausted all my options at this point and it's literally holding up a product launch

S

sethi•6/25/24, 5:28 PM

Hello all @Wrangler dev users! Over the last few months we’ve been working hard to refactor the internal implementation of wrangler’s dev servers. We’re really excited about the stability improvements this brings and the exciting opportunities it will unlock in the future! We’d love for you to give this a go on your Workers and let us know how it goes!

Try it out with the new

--experimental-dev-env

--experimental-dev-env

--experimental-dev-env

--experimental-dev-env flag (shorthand:

--x-dev-env

--x-dev-env

--x-dev-env

--x-dev-env) on wrangler v3.62.0 or newer:

$ npx wrangler@latest dev --x-dev-env
# or
$ npx wrangler@latest dev --remote --x-dev-env

$ npx wrangler@latest dev --x-dev-env
# or
$ npx wrangler@latest dev --remote --x-dev-env

$ npx wrangler@latest dev --x-dev-env
# or
$ npx wrangler@latest dev --remote --x-dev-env

$ npx wrangler@latest dev --x-dev-env
# or
$ npx wrangler@latest dev --remote --x-dev-env

If you come across any bugs feel free to create an issue at https://github.com/cloudflare/workers-sdk/issues/new. We’d also love to hear if it works for you without any bugs! We’ll be actively monitoring for these issues and feedback until July 8th before deciding to enable the flag by default.

⃟

⃟⃞⃟⃞ -THE NOTORIUS Ⱳ.Ø.Ẓ̣̣ ✞♥•6/25/24, 5:33 PM

w

L

Lukinhas•6/25/24, 5:36 PM

W

Ssethi Hello all @Wrangler dev users! Over the last few months we’ve been working hard ...

M

moody 💭•6/25/24, 5:39 PM

it's working for me. but still debugger doesn't work, that's the one thing i want fixed

https://github.com/cloudflare/workers-sdk/issues/5339#issuecomment-2189587023

N

neoney•6/25/24, 5:41 PM

what does the new dev env bring

Ssethi Hello all @Wrangler dev users! Over the last few months we’ve been working hard ...

C

Chinoman10•6/25/24, 9:12 PM

For some feedback (not a bug), since wrangler 'lost' the capability to 'port forward' a dev server, it's been a nightmare to develop a Pages project with Functions...

Regular pages: just ignore wrangler and use 'bun run dev' or whatever you're using; it'll update automatically on file save;

Regular Worker: same thing, just run with wrangler and it'll auto-detects changes automatically and reload;

Pages + Functions: nightmare -- the 'only way' (AFAIK) for it to work is 'bun run build' (or npm or whatever) and then ask wrangler to 'serve' the dist folder (if using Astro, otherwise some other public folder). But the 'build' only does the process once, it doesn't keep rebuilding. And if it kept rebuilding, since the process would 'hang' and not exit, then chaining the commands

bun run build && wrangler pages dev dist

bun run build && wrangler pages dev dist

bun run build && wrangler pages dev dist

bun run build && wrangler pages dev dist would no longer work...

I guess I could simply have two terminals opens, one for hot-rebuilding to the 'dist' folder, and another with wrangler to automatically detect changes in that folder and reload/serve them. But there has to be a better way, right?

L

Louis Rangel•6/25/24, 9:12 PM

I have a problem with the implementation of my site I need helped

LLouis Rangel I have a problem with the implementation of my site I need helped

C

Chinoman10•6/25/24, 9:13 PM

Wrangler help? Or #pages-help ?

L

Louis Rangel•6/25/24, 9:13 PM

How use wrangler in my site make in nextjs and react

P

Paul•6/27/24, 1:14 AM

Whenever I run

dev

dev

dev

dev, the process oftentimes doesn't shut down correctly and it ends up needing to use a different port every time.

I get errors like this:

✘ [ERROR] Address already in use (127.0.0.1:60392). Please check that you are not already running a server on this address or specify a different port with --port.

✘ [ERROR] Address already in use (127.0.0.1:60392). Please check that you are not already running a server on this address or specify a different port with --port.

✘ [ERROR] Address already in use (127.0.0.1:60392). Please check that you are not already running a server on this address or specify a different port with --port.

✘ [ERROR] Address already in use (127.0.0.1:60392). Please check that you are not already running a server on this address or specify a different port with --port.

So I have to run the following:

lsof -i :60392
kill -9 <PID>

lsof -i :60392
kill -9 <PID>

lsof -i :60392
kill -9 <PID>

lsof -i :60392
kill -9 <PID>

Is there a way to avoid this or fix this? I feel like this is some known issue. When I searched about it online, I think folks are saying it's due to the hot-reloading feature, but this seems like a fundamental issue.

C

ccostes•6/27/24, 9:36 PM

Trying to figure out how to set up my local directory structure for a project with Pages and Workers which need to access D1.

Seems like wrangler gnerally expects to be in the same directory as the pages/worker project. Anybody know of examples of a multi-component project like this?

project
- pages_dir
  - src/
  ...
- worker1
  ...
- wranger.toml

project
- pages_dir
  - src/
  ...
- worker1
  ...
- wranger.toml

project
- pages_dir
  - src/
  ...
- worker1
  ...
- wranger.toml

project
- pages_dir
  - src/
  ...
- worker1
  ...
- wranger.toml

C

ccostes•6/27/24, 9:39 PM

I currently have separate the worker and pages projects in separate directories with their own

wrangler.toml

wrangler.toml

wrangler.toml

wrangler.toml, but need to duplicate my D1 schema in both and I think they would have different local DBs when running locally.

Hoping there's a better way to have everything together.

Cccostes I currently have separate the worker and pages projects in separate directories ...

H

Hello, I’m Allie!•6/27/24, 10:21 PM

You can use —persist-to so they point to the same directory when storing data

H

Hello, I’m Allie!•6/27/24, 10:21 PM

Then db instances will be shared

HHello, I’m Allie!You can use —persist-to so they point to the same directory when storing data

C

ccostes•6/27/24, 10:24 PM

Ah perfect, thanks!

M

Mayuresh Choudhary•6/28/24, 6:24 AM

hey hello, i am facing "ERR_RUNTIME_FAILURE": MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. when i execute the "npm run dev" command in my Cloudflare web app

I created this app using "npm create-cloudflare" (v 2.21.9), wrangler (3.62.0)
web app
framework Honojs
no git, no deploy

now when I execute the command "npm run dev" it the gives above error and the development server won't start
i tried executing "wrangler dev" directly (with version < 3.62.0) it runs the application but i don't know whats wrong with create-cloudflare

O

oof2win2•6/28/24, 11:34 AM

so i tried using cf wrangler + devtools to profile my js but i only get

(program)

(program)

(program)

(program) as the profiled code and it runs for the whole duration so it's not very useful

O

oof2win2•6/28/24, 11:35 AM

and it happens also when using

chrome://inspect

chrome://inspect

chrome://inspect

chrome://inspect and connecting using the new Performance tab (though i had to pass the --inspect flag to wrangler to make it connect properly)

O

oof2win2•6/28/24, 11:43 AM

and when i use the example from the web it just gives

(program)

(program)

(program)

(program) as well

R

RazzleD•6/28/24, 5:07 PM

#wrangler help . Am I up to date with all

MMayuresh Choudhary hey hello, i am facing "ERR_RUNTIME_FAILURE": MiniflareCoreError [ERR_RUNTIME_FA...

K

Kimitri•6/28/24, 5:53 PM

the same happened to me

K

Kimitri•6/28/24, 8:14 PM

Someone can answer me this question? did wrangler needs certification ssl to work locally?

KKimitri Someone can answer me this question? did wrangler needs certification ssl to wor...

H

Hello, I’m Allie!•6/28/24, 8:43 PM

For ingress?

HHello, I’m Allie!For ingress?

K

Kimitri•6/28/24, 8:47 PM

no, I'm trying to run wrangler locally and it's getting an error, I just did exactly like the documentation says to start a project "npm create hono@latest" but when I run "npm run dev" I get this error

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
from this
my-app\node_modules\wrangler\wrangler-dist\cli.js:29747
throw a;
^
and searching on google and in this community I found may be the wrangler needs certification to run locally

C

ccostes•6/28/24, 8:54 PM

Also unable to run pages (remix framework created with

create-cloudflare

create-cloudflare

create-cloudflare

create-cloudflare) with wrangler locally (not sure why it thinks the address in use - it's not)

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

KKimitri no, I'm trying to run wrangler locally and it's getting an error, I just did exa...

H

Hello, I’m Allie!•6/28/24, 9:47 PM

That sounds like something else…

H

Hello, I’m Allie!•6/28/24, 9:48 PM

Did you try again?

HHello, I’m Allie!Did you try again?

K

Kimitri•6/29/24, 3:14 AM

yes, I retry all process since run npm create hono@latest again, and still getting the error, I don't know if this happens because I choose the option to don't send metrics to cloudflare, is it forced required?

K

Kimitri•6/29/24, 3:33 AM

and I'm o Windows

HHello, I’m Allie!Did you try again?

K

Kimitri•6/29/24, 3:38 AM

one question, to run Hono I need to install bun? Because I just installed Node, not even Bun

K

Kimitri•6/29/24, 5:27 AM

I'm really frustrated about honor, I don't know what I'm doing wrong, I literally just did everything that documentation from this page says
https://hono.dev/docs/getting-started/cloudflare-workers

and still not working locally, just work when I deploy it, I tried even dockerize it using the dockerfile exemplo provided by documentation and not worked. I don't know if it is because I'm using windows, or something wrong

Cloudflare Workers - Hono

Ultrafast web framework for Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Node.js, and others. Fast, but not only fast.

KKimitri one question, to run Hono I need to install bun? Because I just installed Node, ...

H

Hello, I’m Allie!•6/29/24, 8:10 AM

No, you don’t need bun.

K

Kimitri•6/29/24, 12:25 PM

I finally fixed the issue, the problem is with version 3.62.0 from wrangler, I downgrade it to 3.61.0 and the problem was fixed.

PPorush Manjhi How can I edit wrangler's ```https://github.com/cloudflare/workers-sdk/blob/main...

H

Hello, I’m Allie!•6/30/24, 1:26 PM

It gets bundled. You would need to clone the repo, make your change, then rebuild

N

Nima•6/30/24, 2:39 PM

How do i fix this error, isolated it to a new project and the problem persists (nothing to do with the code, e.g npx create-cloudflare@latest):

npm run dev

dev
wrangler dev

wrangler 3.62.0
-------------------

⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:...\test-wrangler\jolly-pine-7ab4\node_modules\wrangler\wrangler-dist\cli.js:29747
throw a;
^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at #assembleAndUpdateConfig (C:...\test-wrangler\jolly-pine-7ab4\node_modules\miniflare\dist\src\index.js:9161:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Mutex.runWith (C:...\test-wrangler\jolly-pine-7ab4\node_modules\miniflare\dist\src\index.js:3521:16) {
code: 'ERR_RUNTIME_FAILURE',
cause: undefined
}

Node.js v22.3.0

https://github.com/cloudflare/workers-sdk/issues/6170#issuecomment-2198662368

GitHub

🐛 BUG: Received structured exception #0xc0000005: access violation;...

Which Cloudflare product(s) does this pertain to? Miniflare What version(s) of the tool(s) are you using? 3.20240620.0 [Miniflare] What version of Node are you using? 22.3.0 What operating system a...

KKimitri I finally fixed the issue, the problem is with version 3.62.0 from wrangler, I d...

M

Mayuresh Choudhary•7/1/24, 5:18 AM

Yeah I did the same last night and it worked the issue is with the latest version of Wrangler (i.e 3.62.0)

i'm not sure what has changed but it was working fine for me for quite awhile... now i can't either

Similar Threads