`cache.match` checks for a cached value. If it's in the cache, it returns the value, otherwise it re

IIsaac McFadyen `cache.match` checks for a cached value. If it's in the cache, it returns the va...

L

lukas•12/13/23, 12:15 AM

is it looking at the

colo

colo

the worker is being run in, or is it checking the global cache?

i'm just trying to figure out how to lower my latency, cuz im getting 100ms+ for requests outside of the origin, even though they're resulting in a 'cache hit'

Llukas is it looking at the `colo` the worker is being run in, or is it checking the gl...

I

Isaac McFadyenOP•12/13/23, 12:15 AM

There is no global cache. It's checking the cache of the colo the Worker is run in.

I

Isaac McFadyenOP•12/13/23, 12:15 AM

Even tiered caching isn't "global" per-say. But in your case Tiered Cache isn't applicable anyway.

I

Isaac McFadyenOP•12/13/23, 12:16 AM

Are you doing any other processing in your Worker that might cause high response times?

I

Isaac McFadyenOP•12/13/23, 12:16 AM

And can you confirm that the response from

cache.match

cache.match

is actually being returned and the origin isn't being hit anyway?

IIsaac McFadyen There is no global cache. It's checking the cache of the colo the Worker is run ...

L

lukas•12/13/23, 12:16 AM

ok so thats what i was wondering where its requesting that cache

L

lukas•12/13/23, 12:17 AM

ill respond to those in a few, gotta go outside before the sun goes down lol

I

Isaac McFadyenOP•12/13/23, 12:17 AM

Yeah. The colo that the Worker is run in. There may be multiple different colos in a city, and they don't share cache currently.

IIsaac McFadyen Are you doing any other processing in your Worker that might cause high response...

L

lukas•12/13/23, 1:07 AM

This the workflow of whats going on in my app

endpointCreate -> D1, take the created record, turn it into a response, and cache it

endpointCheck -> check `caches.default.match`, if response exists for cacheKey return endpoint response based off that cache, sync both D1 and cache via executionContext.waitUntil(update D1, update cache)

endpointCreate -> D1, take the created record, turn it into a response, and cache it

endpointCheck -> check `caches.default.match`, if response exists for cacheKey return endpoint response based off that cache, sync both D1 and cache via executionContext.waitUntil(update D1, update cache)

endpointCreate -> D1, take the created record, turn it into a response, and cache it

endpointCheck -> check `caches.default.match`, if response exists for cacheKey return endpoint response based off that cache, sync both D1 and cache via executionContext.waitUntil(update D1, update cache)

endpointCreate -> D1, take the created record, turn it into a response, and cache it

endpointCheck -> check `caches.default.match`, if response exists for cacheKey return endpoint response based off that cache, sync both D1 and cache via executionContext.waitUntil(update D1, update cache)

So majority of the time, i am working off of the cached result, and then updating d1 and cache with fresh data

So, based on what I understand now, CF argo routing will determine which

colo

colo

to invoke the worker, in which the worker checks the cache of that

colo

colo

and if its not there it routes back to the origin to retrieve the data

L

lukas•12/13/23, 1:08 AM

Oh and computation is very little, its mainly my caching layer that I'm trying to optimize here

L

lukas•12/13/23, 1:10 AM

With tiered caching, If end user lives on the east, and the

colo

colo

on the east coast does not have the cache, it would retrieve it from another

colo

colo

nearby that might have the cache, and if not, it would go to the origin?

Llukas Oh and computation is very little, its mainly my caching layer that I'm trying t...

H

Hello, I’m Allie!•12/13/23, 7:34 AM

User to Worker Routing is handled by BGP, not Argo

H

Hello, I’m Allie!•12/13/23, 7:34 AM

Basically, the nearest colo to the user(according to their ISP) is chosen

H

Hello, I’m Allie!•12/13/23, 7:34 AM

And according to your plan

B

bun•12/13/23, 11:42 AM

getting

crypto.pbkdf2Sync is not a function

crypto.pbkdf2Sync is not a function

crypto.pbkdf2Sync is not a function

crypto.pbkdf2Sync is not a function when using https://www.npmjs.com/package/cryptr on workers

npm

cryptr

a simple encrypt and decrypt module for node.js. Latest version: 6.3.0, last published: 3 months ago. Start using cryptr in your project by running

npm i cryptr

npm i cryptr

npm i cryptr

npm i cryptr. There are 309 other projects in the npm registry using cryptr.

B

bun•12/13/23, 11:43 AM

not sure how to fix it

Bbun getting `crypto.pbkdf2Sync is not a function` when using https://www.npmjs.com/p...

E

Erisa•12/13/23, 11:50 AM

Based on the code and that error I suspect its trying to use Node.js crypto, which in Workers requires the

nodejs_compat

nodejs_compat

compatability flag https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/ but also probably still wont work without a modification to the library because it

require

require

s

crypto

crypto

crypto

crypto instead of

node:crypto

node:crypto

But once those two hurdles are surpassed,

pbkdf2Sync

pbkdf2Sync

pbkdf2Sync

pbkdf2Syncis listed as supported in our implementattion of Node.js crypto

B

bun•12/13/23, 11:51 AM

B

bun•12/13/23, 11:51 AM

so change

const crypto = require('crypto');

const crypto = require('crypto');

const crypto = require('crypto');

const crypto = require('crypto'); to

import crypto from "node:crypto"

import crypto from "node:crypto"

import crypto from "node:crypto"

import crypto from "node:crypto"?

E

Erisa•12/13/23, 11:52 AM

Something like that yeah, sounds about right

E

Erisa•12/13/23, 11:52 AM

It also uses Buffer so you might need to do something for that if its mandatory https://developers.cloudflare.com/workers/runtime-apis/nodejs/buffer/

B

bun•12/13/23, 11:52 AM

noted

E

Erisa•12/13/23, 11:53 AM

And the compatibility flag to unlock the

node:

node:

node:

node: stuff is just

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

in your wrangler.toml

B

bun•12/13/23, 11:53 AM

oh i didthis

B

bun•12/13/23, 11:53 AM

thats what the error message said to use

E

Erisa•12/13/23, 11:54 AM

The error message lies

B

bun•12/13/23, 11:54 AM

E

Erisa•12/13/23, 11:54 AM

node_compat = true

node_compat = true

node_compat = true

node_compat = true is the old implementation

E

Erisa•12/13/23, 11:55 AM

methinks the error message needs to be updated, I should check if theres an existing issue on workers-sdk

B

bun•12/13/23, 11:55 AM

rip i dont think

createDecipheriv

createDecipheriv

createDecipheriv

createDecipheriv works

E

Erisa•12/13/23, 11:55 AM

B

Bogdan•12/13/23, 3:45 PM

i think i might have posted in the wrong channel: wranglerWebsocket using correctly

B

Bogdan•12/13/23, 3:45 PM

some help would be appreciated

R

rusty•12/13/23, 6:22 PM

Is there a way to deploy javascript module as worker via API? I am trying:

$ curl --request PUT \
        --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \
        --header 'Authorization: Bearer {token_id}' \
        --header 'Content-Type: application/javascript' \
        --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

$ curl --request PUT \
        --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \
        --header 'Authorization: Bearer {token_id}' \
        --header 'Content-Type: application/javascript' \
        --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

$ curl --request PUT \
        --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \
        --header 'Authorization: Bearer {token_id}' \
        --header 'Content-Type: application/javascript' \
        --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

$ curl --request PUT \
        --url https://api.cloudflare.com/client/v4/accounts/{account_id}/{worker_name} \
        --header 'Authorization: Bearer {token_id}' \
        --header 'Content-Type: application/javascript' \
        --data 'export default { async fetch(request) { let response = await fetch(request); new Response("Ok") } }

But getting error:

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "workers.api.error.content_type"
    }
  ],
  "messages": []
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "workers.api.error.content_type"
    }
  ],
  "messages": []
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "workers.api.error.content_type"
    }
  ],
  "messages": []
}

{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "workers.api.error.content_type"
    }
  ],
  "messages": []
}

When I deploy using

wrangler

wrangler

, there is no problem. Is there a dedicated header for mjs?

K

kian•12/13/23, 6:23 PM

https://developers.cloudflare.com/api/operations/worker-script-upload-worker-module

K

kian•12/13/23, 6:23 PM

Change the body to

multipart/form-data

multipart/form-data

multipart/form-data

multipart/form-data and follow that documentation.

K

kian•12/13/23, 6:23 PM

R

rusty•12/13/23, 6:24 PM

thank you! Will try

K

kian•12/13/23, 6:25 PM

You could also refer to how Wrangler does it: https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/src/deployment-bundle/create-worker-upload-form.ts

A

Alexey Ch.•12/13/23, 8:09 PM

Hello! Has anyone encountered such a problem that Real-time Logs do not work? Moreover, for none of my Workers, including those that I haven’t touched for a long time. When I try to start I get the following message: "Could not establish websocket connection. Begin log stream to try again."

A

AA•12/13/23, 8:17 PM

huh. today is a new compatibility date? 2023-12-13

A

AA•12/13/23, 8:19 PM

doesnt list the changes

K

kian•12/13/23, 8:21 PM

Compatibility dates can be any date as long as it isn't in the future. The last date to have a specific change seems to be

2023-12-01

2023-12-01

2023-12-01

2023-12-01 which is

crypto_preserve_public_exponent

crypto_preserve_public_exponent

crypto_preserve_public_exponent

crypto_preserve_public_exponent

A

AA•12/13/23, 8:24 PM

ah ok

A

AA•12/13/23, 8:25 PM

for some reason i thought it always jumped to the last change

C

Chaika•12/13/23, 8:41 PM

for a bit Miniflare/wrangler dev used to get upset and warn if you set your compat date ahead of a current one but that was silenced now

C

Chaika•12/13/23, 8:43 PM

It would log
"[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-05-25". Falling back to "2023-05-18"..."
maybe that's where you got that from?

L

lukas•12/13/23, 10:49 PM

Curious, I am trying to save a new Response in a new Map for memory cache, and after I retrieve the value by cache key from the new Map, and I use the .json method on it, I get this error (only happening in worker code, not in a regular nodejs app

i was getting errors like this

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

<Formatting threw (Error: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

L

lukas•12/13/23, 10:49 PM

Why is that?

`cache.match` checks for a cached value. If it's in the cache, it returns the value, otherwise it re

Similar Threads

Similar Threads

Similar Threads