oh is it I thout it is. So I also have another thing where I am doing a sync between my databases b

oh 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

YYash Bindal (yB)oh is it I thout it is. So I also have another thing where I am doing a sync bet...

Ashley•12/9/24, 8:12 AM

Does 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)

AngusMa•12/9/24, 2:32 PM

Dev tools disappear

KenKiyosaki•12/9/24, 4:36 PM

Anyone experienced "XMLHttpRequest is undefined" error when trying to use fetch?

Bradley•12/9/24, 4:39 PM

Hello, 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: true

headless: true

in the browser creation in ec2. But from what it looks like Cloudflare should be defaulting headless. Has anyone seen this issue and found a way to work around it? I'm logging out the browser version and seeing

Chrome/120.0.6099.321

Chrome/120.0.6099.321

, so maybe it's not headless (or it could be "new" headless, we're likely using old headless on ec2). Update I was able to hack this by using an evaluate call to set overflow hidden on html, but would love a better solution.

Aster•12/9/24, 6:18 PM

Hey, 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

AAster Hey, can I rename a worker from wrangler.toml without issues? even if it has bin...

Bradley•12/9/24, 6:43 PM

You can rename in the dashboard, then update the wrangler file.

Aster•12/9/24, 6:57 PM

Thanks, gonna try

HS•12/9/24, 8:35 PM

Does 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?

CCodex one caveat to this is that it appears that the fetchMock provided by miniflare /...

Codex•12/9/24, 9:40 PM

@cloudflare/vitest-pool-workers

@cloudflare/vitest-pool-workers

: As of

0.5.33

0.5.33

the

AbortSignal

AbortSignal

support has now been added and released, was pretty interesting and fun to work on and hopefully this helps others that are wanting to test their workers correctly handle these

masd4•12/10/24, 10:28 AM

these 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/

Mmasd4 these docs aren't clear enough for me, does this mean that if I set a process.en...

Brett Willis•12/10/24, 10:46 AM

Variables 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.

�

😈 Donkey 💫•12/10/24, 10:58 AM

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?

Cloudflare Docs

Remote-procedure call (RPC) · Cloudflare Workers docs

The built-in, JavaScript-native RPC system built into Workers and Durable Objects.

�

😈 Donkey 💫•12/10/24, 11:02 AM

and it seems this forwarding stub https://developers.cloudflare.com/workers/runtime-apis/rpc/#forwarding-rpc-stubs

does not work with Durable Object?

Abdul•12/10/24, 1:13 PM

Hello

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?

AAbdul Hello Cloudflare recently started supporting Deploying your web applications ( ...

Peps•12/10/24, 1:15 PM

?crossposting

SuperHelpflare•12/10/24, 1:15 PM

Please 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.

PPeps ?crossposting

Abdul•12/10/24, 1:21 PM

Sorry sir.

Since i was not aware which channel my question should go in

I wont repeat this sorry again

AAbdul Hello Cloudflare recently started supporting Deploying your web applications ( ...

Ashley•12/10/24, 1:26 PM

https://developers.cloudflare.com/workers/static-assets/compatibility-matrix/ has a good overview, at least in terms of features

Cloudflare Docs

Workers vs. Pages (compatibility matrix) · Cloudflare Workers docs

Compatibility matrix for asset hosting on Cloudflare Workers and Pages.

AAshley https://developers.cloudflare.com/workers/static-assets/compatibility-matrix/ ha...

Abdul•12/10/24, 1:38 PM

Is 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?

Ashley•12/10/24, 1:50 PM

The 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.

KenKiyosaki•12/10/24, 2:38 PM

Can someone please tell me how I can fix "XMLHttpRequest: is undefined" error in nextjs? This happens when I use "fetch" in API routes

KenKiyosaki•12/10/24, 2:38 PM

Why is this happening and why is no one fixing it?

KenKiyosaki•12/10/24, 2:38 PM

@Community time

KenKiyosaki•12/10/24, 2:39 PM

@cb @codefraw

zegevlier•12/10/24, 2:44 PM

?pings

SuperHelpflare•12/10/24, 2:44 PM

Please 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.

rivage•12/10/24, 9:35 PM

using websocket hiberation api with durable object storage. looks like

webSocketClose

webSocketClose

isn't called when the websocket isn't closed cleanly which causes the duration to build.

is it recommended to use an alarm to clean up the durable object data?

Rrivage using websocket hiberation api with durable object storage. looks like `webSocke...

1984 Ford Laser•12/10/24, 10:30 PM

You 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()

this.state.acceptWebSocket()

KKenKiyosaki Why is this happening and why is no one fixing it?

Isaac McFadyen•12/10/24, 10:43 PM

As has been said above, something about your framework is pollyfilling fetch -> XMLHTTPRequest. This is not a Workers issue.

Isaac McFadyen•12/10/24, 10:44 PM

We 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.

11984 Ford Laser You mustn't be using hibernation correctly as it shouldn't build up any duration...

rivage•12/10/24, 10:52 PM

yes:

  async fetch(request: Request) {
    await this.ensureMessagesInitialized();
    const webSocketPair = new WebSocketPair();
    const [client, server] = Object.values(webSocketPair);
    this.ctx.acceptWebSocket(server);
    return new Response(null, {
      status: 101,
      webSocket: client,
    });
  }

  async fetch(request: Request) {
    await this.ensureMessagesInitialized();
    const webSocketPair = new WebSocketPair();
    const [client, server] = Object.values(webSocketPair);
    this.ctx.acceptWebSocket(server);
    return new Response(null, {
      status: 101,
      webSocket: client,
    });
  }

Rrivage yes: ``` async fetch(request: Request) { await this.ensureMessagesInitial...

1984 Ford Laser•12/10/24, 10:56 PM

Very odd, are you sure that usage is from WS? Any clients staying connected and sending messages repeatedly? What are users broadcasting

11984 Ford Laser Very odd, are you sure that usage is from WS? Any clients staying connected and ...

rivage•12/10/24, 10:59 PM

running locally, have had ~5 people test it, but i think this is due to durable object storage

rivage•12/10/24, 11:00 PM

the documentation says websocketclose will be called whenever the websocket closes to clean up storage

rivage•12/10/24, 11:00 PM

here's the implementation of the

deleteAll()

deleteAll()

async webSocketClose(
    ws: WebSocket,
    code: number,
    reason: string,
    wasClean: boolean,
  ) {
    // cleaning up storage if you want, or remove if you prefer not to delete
    await this.state.storage.deleteAll();
    ws.close(code, "durable object is closing websocket");
  }

async webSocketClose(
    ws: WebSocket,
    code: number,
    reason: string,
    wasClean: boolean,
  ) {
    // cleaning up storage if you want, or remove if you prefer not to delete
    await this.state.storage.deleteAll();
    ws.close(code, "durable object is closing websocket");
  }

rivage•12/10/24, 11:00 PM

i'm curious if i should implement an alarm to do this on an interval

1984 Ford Laser•12/10/24, 11:03 PM

Your 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

1984 Ford Laser•12/10/24, 11:04 PM

I don't even have a distinct

webSocketClose()

webSocketClose()

in my code and I haven't had any issues with duration charges

akashra•12/10/24, 11:32 PM

oof. 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

AAshley The matrix is for the core Pages vs Worker compat, so it’s talking about file-ba...

Abdul•12/11/24, 12:33 AM

Thanks Ashley.

Will dig deeper into these and see what i can find

masd4•12/11/24, 7:32 AM

EDIT: 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

Cannot use assets and tail consumers in the same Worker. Tail Workers are not yet supported for Workers with assets

)))

Aakashra oof. I'm still struggling with figuring out an appropriate practice/handling te...

Ashley•12/11/24, 8:17 AM

Depending how much you need to store in the session, you could always use JWTs to avoid any state

akashra•12/11/24, 8:18 AM

I 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.

Aakashra I absolutely do not want to be transferring that much data to and from a client ...

Isaac McFadyen•12/11/24, 5:14 PM

JWTs can't easily be expunged/expired

True, 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.

Isaac McFadyen•12/11/24, 5:15 PM

This would also be applicable for regular sessions. You don't need to write on every request... if you're worried about the session expiring then just hold off a write until 10 minutes before expiry and then renew at that time.

Mozzy•12/11/24, 8:47 PM

Having some issues testing this myself, so:
Does anyone know if Hono's

getContext()

getContext()

works inside a scheduled event triggered by a cron?
In my scheduled event, I would call a function that interacts with KV by using

getContext()

getContext()

to get the KVNamespace

Mozzy•12/11/24, 8:59 PM

I assume it does not work, because there's no actual request, and therefore no context middleware

Mozzy•12/11/24, 9:26 PM

Is there something wrong with cron and deployments?

I've had a wrangler.toml with

crons = ["0 */1 * * *"]

crons = ["0 */1 * * *"]

deployed for a long time which was working.
Earlier today, I updated that to

crons = ["* * * * *"]

crons = ["* * * * *"]

and deployed. The dashboard UI was still saying

0 */1 * * *

0 */1 * * *

was active, and it was still using that pattern.

Now I just reverted it and deployed

crons = ["0 */1 * * *"]

crons = ["0 */1 * * *"]

, and now the

* * * * *

* * * * *

pattern is the one actually running, despite the dashboard UI saying

0 */1 * * *

0 */1 * * *

is active.

Mozzy•12/11/24, 9:27 PM

Mozzy•12/11/24, 9:33 PM

I just did a deploy of the same exact content, and now it seems to be using the correct cron schedule. It seems that deployments use the previous deployment's cron triggers

async fetch(request: Request) { await this.ensureMessagesInitialized(); const webSocketPair = new WebSocketPair(); const [client, server] = Object.values(webSocketPair); this.ctx.acceptWebSocket(server); return new Response(null, { status: 101, webSocket: client, }); }

async webSocketClose( ws: WebSocket, code: number, reason: string, wasClean: boolean, ) { // cleaning up storage if you want, or remove if you prefer not to delete await this.state.storage.deleteAll(); ws.close(code, "durable object is closing websocket"); }

oh is it I thout it is. So I also have another thing where I am doing a sync between my databases b

Similar Threads