JDoes anyone knows what I can do to make vitest aware of the bindings?
Jvitest.config.js is just: import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
export default defineWorkersConfig({
test: {
poolOptions: {
workers: {
wrangler: { configPath: "./wrangler.toml" },
},
},
},
});
export default defineWorkersConfig({
test: {
poolOptions: {
workers: {
wrangler: { configPath: "./wrangler.toml" },
},
},
},
});
NAny viable workaround to get syntax highlighting in vscode for
.dev.vars file?
Mthe
wrangler deletefunctionality seems a bit dangerous.. it would be nice if I could somehow restrict an API key to only be able to delete workers that were created by that same key... otherwise it could theoretically snipe anything else
VUnable to connect to any of the browser. How to kill or reboot, so that a fresh browser is started or fix these?
BDo people see a big difference in initial worker response times between their staging/production workers? I'm getting a consistent 400ms response time for a worker in my dev environment (which is very rarely called) but in production things are a bit better around 80ms - exact same configuration.
VAnyone from Cloudflare? these browser are running from yesterday and neither I can connect nor close them.
So, my application is offline as I can't start new browser as well. which says error 429, maximum limit: 2 already running...which are stalled
So, my application is offline as I can't start new browser as well. which says error 429, maximum limit: 2 already running...which are stalled
SFollowing these instructions and selecting SvelteKit creates a project set up for Workers Static Assets that can't be deployed?
RAnyone using Remix get Hyperdrive working in dev using
initially I had an error and it was that i needed to configure the correct
remix vite:dev dev server? I can get it working using wrangler dev per https://developers.cloudflare.com/hyperdrive/configuration/local-development/#use-wrangler-dev (i'm using the new Workers, not Pages, FWIW). initially I had an error and it was that i needed to configure the correct
environment in the platform proxy that Remix uses. docs for this are here: https://developers.cloudflare.com/workers/wrangler/api/#getplatformproxy - now that I've set environment, it's loading the binding correctly. but now i'm getting a ERR_UNSUPPORTED_ESM_URL_SCHEME error.
UPDATE: got it working, turns out it was a drizzle/driver configuration problem. If you are looking to set this up, check out https://github.com/ryan0x44/workers-hyperdrive-remix-postgresjs
Cdoes anyone know what the timeline is for this? 3, 6, 9 or 12 months? need it for roadmap planning, thx
FAs far as I know Cloudflare does not give ETAs
H:soontm:
DAny reason I would see tons of queued worker builds if I have a pro plan? I'm assuming I should be able to have 5 concurrent builds? Does this fail when building multiple workers in a monorepo? (example: i made a change to a package that then should update 3 workers but only one at a time builds in my entire account)
AYou can only wait
Dooh nice now all my builds are stuck in "queued" status
EIs there any way to group workers into nice folders or something
Daccording to the docs, there are unlimited build minutes for workers while it is in beta
NHi all, any idea why "nodejs_compat" is not showing in the flags list when trying to edit combability flags from the ui?
NLot of flags are showing, but not "nodejs_compat'".
VWait fir what? It’s already 3rd day. Is CF discontinuing the browser rendering product? Its channel is also archived.
L
L:COOLBEANS: i love workers
PWhy is there a difference for schedule expression in Cloudflare?
For example:
According to crontab.guru (https://crontab.guru/#0_3_*_*_1-5) this should run
But in Cloudflare dashboard it shows as
For example:
0 3 * * 1-5According to crontab.guru (https://crontab.guru/#0_3_*_*_1-5) this should run
At 03:00 on every day-of-week from Monday through Friday.But in Cloudflare dashboard it shows as
Schedule:At 03:00 AM, Sunday through Thursday and also executes like that.VThe browsers stopped working from 6th November. Neither we can start a browser, nor use an existing sessionId.
Mhm, maybe this was never fixed https://community.cloudflare.com/t/workers-cron-triggers-triggering-wrong-days/212893/5
AThat seems to be a bug. Did you create a ticket?
VI opened an issue on Comminuty as the Free plan customer can't create ticket.
https://community.cloudflare.com/t/unable-to-connect-to-any-of-the-browser-sessions/733818
https://community.cloudflare.com/t/unable-to-connect-to-any-of-the-browser-sessions/733818
Jwhen using workers RPC, how can I get the return type of a worker method?
Jin this case a durable object
Jhow do I get the type of mostRecentOrders without making a durable object stub?
JHmm, so it seems the problem is there some type difference somewhere inside date objects
AYou guys are making so many awesome things. Where do I even learn about cloudflare workers. All i see is examples.
FCloudflare Docs
Set up and deploy your first Worker with Wrangler, the Cloudflare Developer Platform CLI.
JI guess I just need to explicitly declare my return values..
Ea NAFS would be really great
VI am on a Worker paid plan, can't open a support ticket?
The support page ask to upgrade the website, but I don't need a website. Just worker paid is enough
The support page ask to upgrade the website, but I don't need a website. Just worker paid is enough
Ois deploying workers down for anyone?
CCorrect. You need a paid zone to be able to open tickets. Everyone is able open Account, billing and registrar tickets.
WWhat are you seeing?
SIf I am using Workers Websocket without Durable Objects (for example using it for listening to queues or as a proxy for another websocket server), how would the pricing work? Is it charged based on per request (hence per websocket connection) and the cpu-time used to process the websocket messages?
FBoth CPU time and per Worker request (not subrequests the worker does)
SMax of 30 seconds of CPU time per invocation - is this happening on the websocket ?
IYes. But keep in mind this is CPU time, not wall time (not time as measured on a clock but time that is measured based on how much compute you are doing)
II also believe a Websocket message resets that limit? (someone would have to confirm though)
FWebsockets seem to have indeed a very long or infinite timeout if I read this correctly -> https://community.cloudflare.com/t/how-can-i-use-a-worker-for-real-time-stuff-limits/325031/2?u=fry69
SOkay, I tested it, it stays longer than 30 seconds. a 2-minute connection was provided.
I30 seconds is cpu time.
ILet me see, I believe I had a tag for this.
I?cpu-time