just set up hyperdrive through a tunnel to a local posgres database, this is amazing!
just set up hyperdrive through a tunnel to a local posgres database, this is amazing!
I^ and also note that CPU time is not the same as wall clock time
Fis it possible to change a environment variable in the worker?
IIYou could technically redeploy the Worker via the Cloudflare API from within the Worker itself, if you really wanted to, but generally other (easier) methods are recommended first, like storing the value in KV.
Yoh is it I thout it is. So I also have another thing where I am doing a sync between my databases
but the external req can take only 100 items per minute
So I tried making cloudflare worker sleep but it failed
Currently doing it using cache state management but too much KV read write
but the external req can take only 100 items per minute
So I tried making cloudflare worker sleep but it failed
Currently doing it using cache state management but too much KV read write
ADoes it need to happen synchronously, before the HTTP response ends? If not, you could use Workflows and do batches of 100 and then a sleep. Alternatively, you could use Queues and publish a message per item and have some rate limiting, but Workflows will be better imo. Only drawback will be you’d need to create sub Workflows at a certain point with the current step limit (e.g. you’d have an effective cap of 51,200 inserts per Workflow)
ADev tools disappear
KAnyone experienced "XMLHttpRequest is undefined" error when trying to use fetch?
BHello, I'm trying to use Browser Rendering to replace a puppeteer ec2 instance, and one difference I've noticed is that in Cloudflare the scrollbars are getting captured when taking a screenshot. I don't see any options or differences from the ec2 side that is different, except for manually setting
headless: trueChrome/120.0.6099.321
AHey, can I rename a worker from wrangler.toml without issues? even if it has bindings, and different environments?
I notice it creates a fresh new worker and doesn't delete the old one
I notice it creates a fresh new worker and doesn't delete the old one
BYou can rename in the dashboard, then update the wrangler file.
AThanks, gonna try 
HDoes the Workers Logs has free tier as well? On the main Workers page it lists that the free Workers tier supports "200,000 log events per day".
But I'm confused if enabling "Workers Logs" (including Invocation logs) under "Observability" in Worker settings is free or not?
But I'm confused if enabling "Workers Logs" (including Invocation logs) under "Observability" in Worker settings is free or not?
C@cloudflare/vitest-pool-workers0.5.33AbortSignal
Mthese docs aren't clear enough for me, does this mean that if I set a process.env variable it could potentially leak into entirely unrelated workers, meaning even workers with a different name? https://developers.cloudflare.com/workers/runtime-apis/nodejs/process/
BVariables in the global scope can be shared only in the same instance of the same worker (think: same process on same machine). Not between different Workers (with different name).
This typically only occurs when multiple requests reach the same data center within a few seconds, then they may get routed to the same Worker instance.
This typically only occurs when multiple requests reach the same data center within a few seconds, then they may get routed to the same Worker instance.
�from what I researching
https://developers.cloudflare.com/workers/runtime-apis/rpc/#promise-pipelining
This (Send functions as parameters) only works with wrangler experimental, until V8 engine supports it officially, am I right?
https://developers.cloudflare.com/workers/runtime-apis/rpc/#promise-pipelining
This (Send functions as parameters) only works with wrangler experimental, until V8 engine supports it officially, am I right?
Cloudflare Docs
The built-in, JavaScript-native RPC system built into Workers and Durable Objects.
�and it seems this forwarding stub https://developers.cloudflare.com/workers/runtime-apis/rpc/#forwarding-rpc-stubs
does not work with Durable Object?
does not work with Durable Object?
AHello
Cloudflare recently started supporting Deploying your web applications ( Nextjs) on workers
that is crazy!
i mean, anybody have tested it? what is the difference between deploying your nextjs app on cloudfare pages vs Workers?
Cloudflare recently started supporting Deploying your web applications ( Nextjs) on workers
that is crazy!
i mean, anybody have tested it? what is the difference between deploying your nextjs app on cloudfare pages vs Workers?
P?crossposting
SPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
ASorry sir.
Since i was not aware which channel my question should go in
I wont repeat this sorry again
Since i was not aware which channel my question should go in
I wont repeat this sorry again
Ahttps://developers.cloudflare.com/workers/static-assets/compatibility-matrix/ has a good overview, at least in terms of features
Cloudflare Docs
Compatibility matrix for asset hosting on Cloudflare Workers and Pages.
AIs it misleading mate?
Or am i getting it wrong?
It says workers dont support file-based routing.
But i just created a /testing route in my nextjs deployed to workers
And it worked.
So what does this docs meant?
Or am i getting it wrong?
It says workers dont support file-based routing.
But i just created a /testing route in my nextjs deployed to workers
And it worked.
So what does this docs meant?
AThe matrix is for the core Pages vs Worker compat, so it’s talking about file-based routing with a Worker without a framework - there’s a lot of differences. If you want Next.js specifics, you’d need to compare what OpenNext supports versus what Next.js itself supports.
KCan someone please tell me how I can fix "XMLHttpRequest: is undefined" error in nextjs? This happens when I use "fetch" in API routes
KWhy is this happening and why is no one fixing it?
K@Community time
K@cb @codefraw
Z?pings
SPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
Rusing websocket hiberation api with durable object storage. looks like
is it recommended to use an alarm to clean up the durable object data?
webSocketCloseis it recommended to use an alarm to clean up the durable object data?
1You mustn't be using hibernation correctly as it shouldn't build up any duration if you aren't sending any messages. Are you calling
this.state.acceptWebSocket()
IAs has been said above, something about your framework is pollyfilling fetch -> XMLHTTPRequest. This is not a Workers issue.
IWe can't help without knowing what framework you're using, and even then we likely can't help. You'll need to talk to the framework authors.
1Very odd, are you sure that usage is from WS? Any clients staying connected and sending messages repeatedly? What are users broadcasting
Rrunning locally, have had ~5 people test it, but i think this is due to durable object storage
Rthe documentation says websocketclose will be called whenever the websocket closes to clean up storage
Rhere's the implementation of the
deleteAll()i'm curious if i should implement an alarm to do this on an interval
1Your issue sounds like something else. It sounds like something else is pinning the server to stay open. I think when it says clean up storage, that's for the server to handle on its own. Having storage after a server is closed won't continue to incur duration charges
1I don't even have a distinct
webSocketClose()
Aoof. I'm still struggling with figuring out an appropriate practice/handling technique for session management and data caching to reduce hits to D1, DO or KV services - especially given the relative high cost of writes to those services to update session caches with any request 
AThanks Ashley.
Will dig deeper into these and see what i can find
Will dig deeper into these and see what i can find
MEDIT: The answer is that I had to upgrade to the latest wrangler and compatability date. (((old question: hi, according to these docs tail workers are supported for workers with assets but when I try to deploy, it says:
Cannot use assets and tail consumers in the same Worker. Tail Workers are not yet supported for Workers with assets
ADepending how much you need to store in the session, you could always use JWTs to avoid any state
AI absolutely do not want to be transferring that much data to and from a client over repeated calls or in a JWT. Also, JWTs can't easily be expunged/expired. I don't know why whenever I try to address this problem someone always insists on JWTs when they're just not an appropriate solution to a problem like this.
IJWTs can't easily be expunged/expiredTrue, but in your initial question you were concerned about writes to KV/DO/D1. If you validated the JWT on every request, it would still only be a a one-time write, and then reads after that, and if you wanted to expire it for some reason it would be 1 extra write.
