MI need crypto function for implement cache aside pattern using kv
Mexample
Dyou can use that just fine with the flag too
Mits not working
Mwhen node_compat = true
MCan i use crypto and pg together?
Mnode_compat = true
compatibility_flags = [ "nodejs_compat" ]
so confused between these two
compatibility_flags = [ "nodejs_compat" ]
so confused between these two
MCloudflare Docs
This example shows you how to connect Hyperdrive to an Amazon Relational Database Service (Amazon RDS) Postgres or Amazon Aurora database instance.
MAs per documentation it says I need node_compat = true
MWhich is not working with crypto
JSadly you can't use
nodejs_compatnode_compatnode_compatnodejs_compatSadly Hyperdrive requires
node_compatpgpostgres.jsnodejs_compatI just want to use crypto module
MThere is no other way I can do with pg?
MI need that for generating hash and use that for caching the queries using kv
MI appreciate your help.
IIf this is for non-cryptographic purposes you can use
crypto.subtleJust do a
digest
Iexactly this
Ii use these functions to create SHA-256 hash from a string:
MThanks guys!
MI will give it a try
HHey are you sure about this? I'm using the flag and postgres.js with hyperdrive and caching appears to be working (altough there is some other performance issues)
SDoes a call to a RPC function count as an additional request? Or is it "free" to use RPC function within Workers? The docs don't mention this, so I assume it's not being billed. But want to be sure.
HIIRC, a call to function on an RPC Stub is free. A call to a function on a DO/Service Binding Stub is billed
YHi, I have a little problem but I think it's a bug so I'd rather share it. In a dev environment, with one worker communicating with another using RPC, and with an environment variable configuration for dev and prod like this :
My Worker A calling Worker B can't find a worker with the name I assigned to Worker B.
Command that works:
npx wrangler dev -c authentification/wrangler.toml --port 9002
Command that doesn't work:
npx wrangler dev -c authentification/wrangler.toml --env dev --port 9002
By adding the "env" property, it no longer finds the Worker
My Worker A calling Worker B can't find a worker with the name I assigned to Worker B.
Command that works:
npx wrangler dev -c authentification/wrangler.toml --port 9002
Command that doesn't work:
npx wrangler dev -c authentification/wrangler.toml --env dev --port 9002
By adding the "env" property, it no longer finds the Worker
KEnvironments change the name of the Worker
KIf you have
name = "foo"env.dev--env devfoo-dev
YOh okay
YMake sense now, thanks
LIs it possible to have a scheduled worker call to a HTTP worker via a binding? All the examples I see mention passing on the
request.urlfetch()Ah okay, thanks!
Lis there an expected delay from a request happening to it showing up on the metrics page? 
Ldo tail workers only work for fetch requests?
KShould work for everything - it's the same stuff that powers
wrangler tailhmm.
Ldo i maybe have it setup wrong?
i have this in my wrangler.toml with the main file exporting fetch, scheduled and queue handlers.
i have this in my wrangler.toml with the main file exporting fetch, scheduled and queue handlers.
KAnd your Tail Worker isn't being invoked?
Lnope
Lignore me, i wasnt looking at the correct tab.
Odoes CF have some product which allows pubsub for clients? i only need sub so i thought of polling and websockets, but was wondering if cf has something better for scale
ZNot an employee, but the startup time you're referring to is the startup limit. As in, your worker needs to be able to start up within that time for it to run at all.
A Worker must be able to be parsed and execute its global scope (top-level code outside of any handlers) within 400 ms. Worker size can impact startup because there is more code to parse and evaluate. Avoiding expensive code in the global scope can keep startup efficient as well.
ZAre you seeing slow cold starts? What promted this question?
ZAs far as I know that's still the case. And you're right that a larger script results in a longer cold-start time, so if you require fast starts make sure to keep your worker small.
