you're averaging a lot of cpu time per execution
you're averaging a lot of cpu time per execution
Nyes
Nyeah its a worker that goes through all database stuff that hasnt been processed and sends webhooks
Nive added a try catch over the main functions
Nand deployed it
Nsuddenly its green, and i have logs
Nand no logs errored
N:thinkRoll:
Wyeah tail should be fine, i can check one of my workers real quick
Nno clue what that was about.
Ntail working now
Nthe worker wasnt working for like a day i think
Nended up with
(warn) Log size limit exceeded: More than 128KB of data (across console.log statements, exception, request metadata and headers) was logged during a single request. Subsequent data for this request will not be recorded in logs, appear when tailing this Worker's logs, or in Tail Workers.
because it did so much at once lolWhaha
Nactually something's still wrong with it
Nbut the code might be wrong
Nill research whats goign on
N
Nthis is mostly time waiting for fetch tho, so should be fine?
Nright?
Wyep
Nlmao
Ncoworker typed a var as any and db field names were outdated
Nhopefully works now
NWhen I deploy a worker with wrangler, all variables will get reset to the ones in wrangler.toml, except for ones that have been encrypted?
Nand back to no tail output -_-
N"It can take up to 30 minutes before events are displayed in Past Cron Events when creating a new Worker or changing a Worker’s name."
Nis it the same for wrangler tail
Ncus damn nothing after i redeployed
Wwe should update that message
Wanyway, no, tail should be basically instant
Nhm
Ni dont get anything
N;/
Nand seems to have been every other minute?
Nbruh im getting normal logs, not the cron ones though
Nand the cron events are delayed by like at least 13 minutes rn
Nso not sure if it runs
NI redeployed from wrangler and now I have logs
NPrevious deploy was from browser
NNot sure
JAre there example repos of Durable Object RPC + vitest integration?
I'm running into trouble with it throwing
I'm running into trouble with it throwing
The receiving Durable Object does not support RPC... when running tests attached to it. Repro here: https://github.com/its-jman/workers-types-reproNWorker accumulated too much stuff and didnt seem to be working
NDisabled it, ran it on prod db in local env, took like 2 minutes to run
Nreenabled on CF
Nand hopefully should be fine now
KTry adding the
rpc compatibility flag into your Wrangler.jsonJOk, new problems. When running tests against a durable object I'm getting
I was able to resolve it without RPC by following the error found in this thread: vitest-integration-beta
But it seems like it's causing issues regardless in RPC
Failed to pop isolated storage stack frame in... I was able to resolve it without RPC by following the error found in this thread: vitest-integration-beta
But it seems like it's causing issues regardless in RPC
YDoes worker have problem with firebase admin ? I can't seem able to connect to firebase from cloudflare workers.
KAnyone know pricing for RPC?
AWhen you run a worker locally with
npx wrangler dev --remote