yeah if you make it unbound/unbundled

How to do that?

What is globalThis? Is that some DO magic constant?

It's not a Cloudflare thing: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis

Wow thankyou

Would using globalThis remove the execution limit of the timer?

no, it's only needed in Vanessa's code because we've got a local alias for setTimeout so it's a way to call the original

1 problem I had using timers was if the timer called another settimeout, eventually it will die

that code is a shim to change set/clearTimeout to still timeout but with a NOP - this is to get around a bug with the CF env

say if I have a DO with constantly >1 connected websockets. if any of those requests into the DO set off a setTimeout, then that setTimeout operates in singleshot mode, eventually it will die

but I want it to keep ticking as it detects if a client become a zombie socket

it sounds pretty similar to what I'm doing. If you're setting a new timeout in your timeout handler, you don't need to worry about it dying (for that reason, anyway)

You probably want to use the persistent storage anyway, as DOs might die for other reasons (error, hardware failure, CF moving your DO). Depends on your project, of course

for me if i set new timeout (inside original timeout) it still expired eventually (and the DO did not restart). but i did not use globalThis, are you using globalThis?

I wasn't previously, but it should be the same function, it's just a more qualified path to it

ignore that

my timeouts are zombie checks and game timers. I'm not finding the DO can die when websockets are connected, no matter what the timers are doing

i have it like

and do_tick checks if this.ticking == false -> setTimeout, else ignore

so the first request to spin up the DO starts the tick

depending how many clients are connected, eventually this tick dies

the moreclients the faster it dies

Do you know about the 10,000 limit on setTimeouts?

You're hitting that limit if you see the error

You have exceeded the number of timeouts you may set

no what is this limit

how to avoid it?

use setInterval?

i was using setTimeout as a oneshot loop, i could use setInterval and drop the call if the work is not done yet

Ok, I think this is your problem then. setTimeout and setInterval are limited to 10k per worker. It's from before DOs were a thing. Good news: they're working on fixing it. Bad news: no workaround atm (that I know of, anyway)