looks like there is an ongoing issue here: https://github.com/cloudflare/workers-sdk/issues/3289

GitHub

🐛 BUG: JSG lock error when running locally · Issue #3289 · cloudfla...

Which Cloudflare product(s) does this pertain to? Wrangler What version of Wrangler are you using? 3.0.0 What operating system are you using? Windows 10 Describe the Bug I'm trying to run Remix...

19 Replies

Magic GregOP•16mo ago

nvm - looks like it's "When doing multiple storage.put " based on this: https://github.com/cloudflare/workerd/issues/706#issue-1724611473

GitHub

error: took recursive isolate lock; kj::getStackTrace() on `stora...

I get this error: workerd/jsg/jsg.c++:133: error: took recursive isolate lock; kj::getStackTrace() = 1004af23b 100750017 100772f97 100772f1b 101b9be03 1009e7e0b 10094f88f 10094fab7 101b6e68f 10083f...

Magic GregOP•16mo ago

anyone else seeing this when scheduling alarms from DurableObject ?

Magic GregOP•16mo ago

if i decline i'll see this error: batch: cannot open lockfile /usr/lib/cron/jobs/.lockfile: Operation not permitted

mihaaai•16mo ago

Hey there! Hope it's the right place to address this but I'm getting a strange error that I cannot figure out about types I'm trying to create a WebsocketPair but looks like the accept() method is invisible to TypeScript even though it's declared in it's class, you got any idea what am I doing wrong? Also the EventTarget linting suggest another No base constructor has the specified number of type arguments I've tried with both the experimental and the 2023-07-01 workers-types but the intellisense still complains

MrBBot•16mo ago

Hey! 👋 It looks like you might be (inadvertently) loading TypeScript's default DOM or WebWorker lib types. @cloudflare/workers-types is incompatible with these. Make sure you only have esnext in your tsconfig.json's compilerOptions.lib array. If that's the case, you might be importing a library which references these types. Unfortunately, there's not much you can do in this case, short of finding an alternative package. skipLibCheck: true might help, but I think that would still bring in the incompatible types.

mihaaai•16mo ago

Thanks for that, I had indeed an array with also "WebWorker" there, after removing it the error dissapeared!

Cat•16mo ago

Just want to flag that I'm also seeing intermittent workerd segfaults on a Mac, but it's likely a different cause. I'm guessing it's Durable Objects + Hibernateable WebSockets -- not entirely sure what's causing it, but it sounds like it could be related (it seems to happen randomly, but it could be something where it happens on a websocket disconnect or something so I'm not noticing it).

workerd/util/symbolizer.c++:98: 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>`.
*** Received signal #11: Segmentation fault: 11
stack:

workerd/util/symbolizer.c++:98: 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>`.
*** Received signal #11: Segmentation fault: 11
stack:

Using the most recent workerd (the one that wrangler 3.16.0 ships with)

Unknown User•15mo ago

Message Not Public

Oscar🏖•15mo ago

I'm getting these errors when running my worker locally:

workerd/server/server.c++:2518: error: Uncaught exception: kj/async.c++:212: disconnected: worker_do_not_log; Request failed due to internal error
stack: 102b84093 103a9c963 103aa3f0b 103a9999f 102178ebf 10217c56b 10217c37f 10217c367 103b11f0f 103b1216b 103b1065b 1021701ab 182fed057 103a93d10 102bab32c 102869678 10257e0cc 10257e45b 10245cb44 102b6a080 102b6d490

workerd/server/server.c++:2518: error: Uncaught exception: kj/async.c++:212: disconnected: worker_do_not_log; Request failed due to internal error
stack: 102b84093 103a9c963 103aa3f0b 103a9999f 102178ebf 10217c56b 10217c37f 10217c367 103b11f0f 103b1216b 103b1065b 1021701ab 182fed057 103a93d10 102bab32c 102869678 10257e0cc 10257e45b 10245cb44 102b6a080 102b6d490

workerd/jsg/jsg.c++:136: error: took recursive isolate lock; kj::getStackTrace() = 1021ba9ef 102479f07 10249095b 1024908df 103ac9107 102819493 10281a1af 10277eaff 10277ed27 103a9aadf 10257de07 103a9ae07 10257e8eb 103a9ae07 10245b1c7 103a9c78b 103a9ae07 10245bdbb 103a9bab3 103a9aadf 10245c4f7 103a9ae07 10245c623 103a9bab3 103a9aadf 10245ca07 103a9ae07 10245dad3 103a9bab3

workerd/jsg/jsg.c++:136: error: took recursive isolate lock; kj::getStackTrace() = 1021ba9ef 102479f07 10249095b 1024908df 103ac9107 102819493 10281a1af 10277eaff 10277ed27 103a9aadf 10257de07 103a9ae07 10257e8eb 103a9ae07 10245b1c7 103a9c78b 103a9ae07 10245bdbb 103a9bab3 103a9aadf 10245c4f7 103a9ae07 10245c623 103a9bab3 103a9aadf 10245ca07 103a9ae07 10245dad3 103a9bab3

Happy to help debug further! Pretty lost right now

MrBBot•15mo ago

Hey! 👋 Is your worker still working, or are you seeing an error response? workerd currently logs a few “errors” in normal operation that are safe to ignore. I know the 2nd one is completely fine, but not sure about the first.

Oscar🏖•15mo ago

The 2nd one doesn't seem to affect anything, but the first one seems correlated to these logs for failed requests happening in production

captain•15mo ago

hey guys, I have been struggling all day with a 525 error code. Trying to run a fetch request...that works in the sandbox of the api I am making a request to without issue, as well as in postman, but when running from my worker app....525. What's crazy is it was working not too long ago. That said, I am reading here: https://community.cloudflare.com/t/ssl-525-problem-when-calling-an-api-from-cloudflare-worker/356930/13 that the only solution is to create a ticket with cloudflare and that its related to the cloudflare not handling the ssl handshake properly. Is that true or does anybody here have any other suggestions? Thank you

Cloudflare Community

SSL 525 problem when calling an API from Cloudflare Worker

The problem was not when displaying the page, but rather when submitting the subscription form (calling Revue API with a POST request) The CF proxy was already turned on: And we can subscribe successfully with these 2 URLs (same deployment) https://cf.thisweekinreact.com/ https://this-week-in-react.pages.dev/ I did not change anything si...

captain•15mo ago

i am on the free plan and now cloudflare seemed to remove technical support...so am I SOL..any cloudflare devs on here? This error comes when trying to reach an endpoint https://sandbox.dev.clover.com/v3/merchants/SOMEID/order_types

kian•15mo ago

I’d recommend asking in #workers-help - this channel is just for the open-source runtime.

Unknown User•15mo ago

Message Not Public

MrBBot•15mo ago

Working on it as we speak 🙂 (https://github.com/cloudflare/workers-sdk/tree/bcoll/vitest-pool-workers/packages/vitest-pool-workers) not quite ready for release yet but getting there. 🙂 Hoping to do an initial pre-release in the next few weeks, or early next year.

huw•15mo ago

(Just FYI I have an open PR to mute the ‘recursive isolate lock’ warning—it’s absolutely safe to ignore)

GitHub

Add took recursive isolate lock warning to workerd output excepti...

This PR adapts the code in #4341 to resolve cloudflare/workerd#706 (or, at least, it suppresses the warnings from it). @kentonv says the took recursive isolate lock warning doesn’t represent any ac...

Danny Zhao•15mo ago

Hello! Hope it's the right place to ask the question. I'm trying to build a Rust wrapper for workerd. Do you have any suggestions? I want to know if workerd can worked by ffi link.

zegevlier•15mo ago

What are you hopeing for the wrapper to do? You might be better off emulating what miniflare does, starting a sub process running workerd.

Gaming

Programming

looks like there is an ongoing issue here: https://github.com/cloudflare/workers-sdk/issues/3289

Did you find this page helpful?