upgraded to wrangler 3.1.2 to use local https option, but get the following error: ```workerd/util/

upgraded to wrangler 3.1.2 to use local https option, but get the following error:

workerd/util/symbolizer.c++:95: 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>`.
*** Fatal uncaught kj::Exception: kj/async-io-unix.c++:945: failed: ::bind(sockfd, &addr.generic, addrlen): Address already in use; toString() = 127.0.0.1:9999
stack: 1021761bf 102175f57 1021737ef 100911083 100911244 10091194c 1008dc91f 1008e032b 1008e015f 1008e0147 1021ac0db 1021ac337 1021aaa8f 1021aa85f 1008d41ab 186ce7f27

workerd/util/symbolizer.c++:95: 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>`.
*** Fatal uncaught kj::Exception: kj/async-io-unix.c++:945: failed: ::bind(sockfd, &addr.generic, addrlen): Address already in use; toString() = 127.0.0.1:9999
stack: 1021761bf 102175f57 1021737ef 100911083 100911244 10091194c 1008dc91f 1008e032b 1008e015f 1008e0147 1021ac0db 1021ac337 1021aaa8f 1021aa85f 1008d41ab 186ce7f27

workerd/util/symbolizer.c++:95: 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>`.
*** Fatal uncaught kj::Exception: kj/async-io-unix.c++:945: failed: ::bind(sockfd, &addr.generic, addrlen): Address already in use; toString() = 127.0.0.1:9999
stack: 1021761bf 102175f57 1021737ef 100911083 100911244 10091194c 1008dc91f 1008e032b 1008e015f 1008e0147 1021ac0db 1021ac337 1021aaa8f 1021aa85f 1008d41ab 186ce7f27

workerd/util/symbolizer.c++:95: 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>`.
*** Fatal uncaught kj::Exception: kj/async-io-unix.c++:945: failed: ::bind(sockfd, &addr.generic, addrlen): Address already in use; toString() = 127.0.0.1:9999
stack: 1021761bf 102175f57 1021737ef 100911083 100911244 10091194c 1008dc91f 1008e032b 1008e015f 1008e0147 1021ac0db 1021ac337 1021aaa8f 1021aa85f 1008d41ab 186ce7f27

using node 16.20.0 (tried switching to 18 but the error still occurs).
wrangler.toml setting:

[dev]
ip = "127.0.0.1"
port = 9999
local_protocol = "https"

[dev]
ip = "127.0.0.1"
port = 9999
local_protocol = "https"

[dev]
ip = "127.0.0.1"
port = 9999
local_protocol = "https"

[dev]
ip = "127.0.0.1"
port = 9999
local_protocol = "https"

EDIT: strangely, it works when passing the flags inline:

wrangler dev src/main.ts --live-reload --local-protocol https --port 9999

wrangler dev src/main.ts --live-reload --local-protocol https --port 9999

wrangler dev src/main.ts --live-reload --local-protocol https --port 9999

wrangler dev src/main.ts --live-reload --local-protocol https --port 9999

anyone knows why?

Ggutterball upgraded to wrangler 3.1.2 to use local https option, but get the following erro...

MrBBot•7/10/23, 11:09 AM

Hey!

Could you double check that you don't have any other wrangler devwrangler dev sessions running? Ideally restart your computer, but otherwise try pkill workerdpkill workerd.

MMrBBot Hey! 👋 Could you double check that you don't have any other `wrangler dev` sess...

gutterballOP•7/10/23, 3:32 PM

hey @mrbbot , thanks for replying! I restarted my machine and indeed it works! I'm still getting the errors in the console, but the app works which is what's important. thanks!

Ggutterball hey @mrbbot , thanks for replying! I restarted my machine and indeed it works! I...

MrBBot•7/10/23, 5:22 PM

Excellent! If you're seeing this regularly it's possible we've got an issue. Please open a GitHub issue if this becomes a problem for you.

kian•7/11/23, 11:21 AM

So the putput promise never resolves?

vassbence•7/11/23, 4:38 PM

i'm getting

workerd/util/symbolizer.c++:95: 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>`.
workerd/jsg/util.c++:277: info: exception = kj/async-io-unix.c++:1526: disconnected: connect(): Connection refused

workerd/util/symbolizer.c++:95: 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>`.
workerd/jsg/util.c++:277: info: exception = kj/async-io-unix.c++:1526: disconnected: connect(): Connection refused

vassbence•7/11/23, 4:38 PM

in unstable_dev()unstable_dev()

vassbence•7/11/23, 4:44 PM

it will has to do something with running in vitest setup files, as it does not happen when i start the unstable_devunstable_dev in a regular test file

micromashor•7/11/23, 7:46 PM

is there a flag to force wrangler to run in non-interactive mode?

micromashor•7/11/23, 7:47 PM

I guess the hacky way is to pass /dev/null/dev/null as its stdin

Original message was deleted

micromashor•7/11/23, 8:26 PM

thanks

micromashor•7/11/23, 8:28 PM

actually that's probably the easiest way bc I'm running it from

make

make

, so that would avoid having to add </dev/null</dev/null every time

micromashor•7/11/23, 8:29 PM

yup

hanpolo•7/12/23, 9:11 PM

So does anyone know of a guide on how to test Durable Objects with the new Wrangler 3.1.2? I cannot get any of my old tests to work. For instance, should I still be specifying environment: minflare? Because when I do it simply fails to find my durable object. Or should I set
"vitest-environment-miniflare/globals" in tsconfig.json?

Hhanpolo So does anyone know of a guide on how to test Durable Objects with the new Wrang...

MrBBot•7/13/23, 9:45 AM

Miniflare's Vitest environment hasn't been upgraded to v3 yet. We're working on it, but it's going to take a while...

If you've got existing Vitest tests written, I'd stick with v2 for the time being.

Muhymin•7/13/23, 11:26 AM

! I am having an issue with wrangler tailwrangler tail that it always exits automatically after some time. Is it the expected behavior?? I didn't find any solution for this online.

MMrBBot Miniflare's Vitest environment hasn't been upgraded to v3 yet. We're working on ...

hanpolo•7/13/23, 11:43 AM

Thanks for the response. I came to that conclusion yesterday, removed miniflare from my tests and wrote my own mocks so I could run tests for 3.1.2. looking forward to getting the miniflare update sometime in the future.

Muhymin•7/13/23, 12:03 PM

Off-Topic: @mrbbot I really thought you were a bot who creates threads. And I wondered why the bot didn't create a thread from my message

Ssimpsojo Seems it should just work (TM), but didn't for me (On windows, I got the error: ...

Adam•7/13/23, 8:40 PM

If there's an issue with expected functionality, please help us by filing an issue here https://github.com/cloudflare/workers-sdk/issues so we can take a look!

GitHub

Issues · cloudflare/workers-sdk

Home to Wrangler, the CLI for Cloudflare Workers® - Issues · cloudflare/workers-sdk

beelzabub•7/14/23, 9:01 PM

Does Miniflare 3 have any mechanism to overwrite what domain names map to (within the API, not wrangler)? For example, if my worker is doing a fetch to https://my.custom.domain.comhttps://my.custom.domain.com, I would like that to get routed to a localhost server for CI testing purposes without changing the URL within the code.

kian•7/14/23, 9:30 PM

Not yet https://github.com/cloudflare/miniflare/discussions/588#discussioncomment-5995047

Bbeelzabub Does Miniflare 3 have any mechanism to overwrite what domain names map to (withi...

MrBBot•7/14/23, 9:54 PM

Put a PR up, https://github.com/cloudflare/miniflare/pull/629, still planning to add support for fetch mocks like in Miniflare 2

ajgeiss0702•7/15/23, 1:16 AM

secrets are seperate for each worker, right?

James•7/15/23, 1:18 AM

yep!

James•7/15/23, 1:18 AM

I believe account-wide secrets is a feature that will be coming, but no ETA

ajgeiss0702•7/15/23, 1:21 AM

ok, cool. If i put a secret before publishing the worker, will it pick it up when published? Or will I need to wait to put secrets until after publishing?

ajgeiss0702•7/15/23, 1:22 AM

I guess ill find out in a few minutes anyway

James•7/15/23, 1:23 AM

I think you will have to create and publish the worker once before you add secrets? But honestly I've not tried that workflow in quite a while - let me know what happens

ajgeiss0702•7/15/23, 1:25 AM

will do

ajgeiss0702•7/15/23, 1:26 AM

looks like the pre-put secrets worked

James•7/15/23, 1:26 AM

awesome to hear!

vassbence•7/15/23, 6:38 PM

My tests using unstable_dev()unstable_dev() and R2 fail in CI. Has anyone seen something similar? Sadly giving a longer timeout (5+sec) for the test doesn't seem to fix the problem. The test finishes in local in 24ms.

James•7/15/23, 6:41 PM

That's not a lot of info to work with unfortunately. Are these tests that used to work and no longer? Is it just the R2 tests - do other tests work? What kind of debugging have you done to see where they seemingly hang? What versions of wrangler, etc. are you using? Can you create a minimal reproducible example of a single test that works locally but then fails in CI so we can reproduce?

vassbence•7/15/23, 6:42 PM

Sadly loglevel: debugloglevel: debug doesnt show any errors, test just hang with a simple env.BUCKET.putenv.BUCKET.put

vassbence•7/15/23, 6:42 PM

Latest wrangler and all of that, it's a fresh repo

vassbence•7/15/23, 6:42 PM

Sure I can do a small repro but how should I go around the CI part? host it as a public github repo and do an action there?

vassbence•7/15/23, 6:43 PM

and yes, its R2 only

James•7/15/23, 6:44 PM

Something like that and an issue on the workers-sdkworkers-sdk repo would probably be the best idea, yeah

IItalyPaleAle Is there a way to start `wrangler dev` pointing to a different `.dev.vars`? My c...

Hello, I’m Allie!•7/15/23, 11:45 PM

I don’t think so. The only thing I could think of is temporarily renaming the existing .dev.vars

kian•7/15/23, 11:45 PM

Why wouldn't you be able to use unstable_dev?

kian•7/15/23, 11:45 PM

upgraded to wrangler 3.1.2 to use local https option, but get the following error: ```workerd/util/

Similar Threads

Similar Threads

Similar Threads