httpx/aiohttp are just patched to normal js fetch <https://github.com/cloudflare/workerd/blob/main/s

httpx/aiohttp are just patched to normal js fetch https://github.com/cloudflare/workerd/blob/main/src/pyodide/internal/patches/aiohttp.py, would have same limitations with ssl/timeouts

Nesk•6/19/24, 4:45 PM

Hi everyone, is there any way to use the Rate Limiting API with a custom duration period? The documentation says:

Period: the duration of the period, in seconds. Must be either 10 or 60

Is this some kind of limitation during the beta? I would like to use a 1 hour duration period, or more.

CChaika httpx/aiohttp are just patched to normal js fetch <https://github.com/cloudflare...

Nicolas•6/19/24, 4:50 PM

@Chaika thank you for the details that's interesting

Original message was deleted

Nesk•6/19/24, 4:57 PM

Yes, as in “yes, you can use a custom period duration”?
Or yes, as in “yes, this is a beta limitation”?

Nesk•6/19/24, 4:58 PM

thank you for your help

cron•6/19/24, 6:36 PM

possibly a silly question - i have a worker that i created 5 months ago and it defaults to a file named index.js for fetch

but i created a worker now, which defaults to worker.js for fetch calls, even if i try to change it to index.js - has something changed with the archetype between the last five months, or did i use a different template while setting up and have forgotten about it?

cron•6/19/24, 6:39 PM

AH. I figured it out - I guess it defaults to wrangler projects now when you're trying to create a blank worker?

cron•6/19/24, 6:39 PM

has it always done that? i feel like i am having amnesia lol

madi. ™•6/19/24, 6:58 PM

i am crazy new to server hosting. i have a discord bot that is already coded up and i just need to upload it to cloudlfare, is there a way to do that..?

Mmadi. ™i am crazy new to server hosting. i have a discord bot that is already coded up ...

Hard@Work•6/19/24, 7:00 PM

What language is the bot written in? Does it use the Gateway, or just Slash Commands?

HHard@Work What language is the bot written in? Does it use the Gateway, or just Slash Comm...

madi. ™•6/19/24, 7:01 PM

i havent enabled slash commands, not sure about the gateway thing, im basically self hosting a log bot that recently went down. called Logger

madi. ™•6/19/24, 7:02 PM

written in javascript

Mmadi. ™i havent enabled slash commands, not sure about the gateway thing, im basically ...

Hard@Work•6/19/24, 7:03 PM

Yeah, I don't think that would be able to be run on any Cloudflare products at the moment. You would need a VPS or something like Fly/AWS Lambda(or another service that can run Node)

madi. ™•6/19/24, 7:03 PM

ah i see, ok thank you :)

Brett Willis•6/19/24, 9:11 PM

Hey, can anyone give a gauge of the hardware performance underpinning the Workers platform? Given that "CPU time" is a billed metric, and we have no gauge of how many ops/sec or something the isolate/thread can do, it is quite arbitrary and hard to gauge. Any hardware acceleration for crypto operations? I'm guessing the hardware is constantly evolving and different depending on the data centre... but perhaps someone can comment or improve my understanding...?

For example, verifying JWTs using the SubtleCrypto API is common on every request for an API, and also a computationally heavy operation. And just from experience I'm getting the feeling that the CPU available to Workers feels pretty slow compared to other "single vCPU" runtimes I've used... any insights?

Original message was deleted

Brett Willis•6/19/24, 9:31 PM

Ah thanks! I see in https://blog.cloudflare.com/cloudflare-gen-12-server-bigger-better-cooler-in-a-2u1n-form-factor their Gen 11 fleet was AMD Milan 7713, but doesn't look like they actually confirmed what their Gen 12 (2024) fleet is going to be...

Brett Willis•6/19/24, 9:39 PM

Also I've been finding that our Workers get evicted crazy fast. Like it gets evicted in under 5 seconds a lot of the time, and then does a cold start for a request to the same data centre 5 seconds later. Is that normal or what? On a cold start it also has to do a bit of CPU work like importing crypto keys etc.
The docs say that the

env

env

object can be equal by reference until the env variables or bindings change, so we cache our state on the env object but it gets evicted crazy fast.

Original message was deleted

Brett Willis•6/19/24, 9:42 PM

I've got one too that verifies a JWT and sends a response, and it tends to use upwards of 80ms CPU per request which feels like a lot. But I've got a feeling that a lot of that CPU is related to spinning up a cold environment as it goes down significantly when I ramp up the RPS to keep the instance alive.

Original message was deleted

Brett Willis•6/19/24, 9:44 PM

Using

jose

jose

Original message was deleted

Brett Willis•6/19/24, 9:46 PM

Ah I see, that is interesting... It felt natural because the application state is explicitly tied to the env config, and the docs says it's the same object reference between requests. If using global vars I'd have to reason about invalidating when env config changes.
Caching on env does seem to work, but it just seems to get evicted pretty promptly...

Original message was deleted

Brett Willis•6/19/24, 9:46 PM

Are there any docs about this env being a software update that causes eviction?

Brett Willis•6/19/24, 9:52 PM

Hmm ok. Well it's worth a try, I'll try caching on

globalThis

globalThis

instead of

env

env

and let you know if that changes our crazy-fast eviction.

Ttoby357 I'm wondering if this would cache the result from a sub worker

Hello, I’m Allie!•6/20/24, 7:08 AM

Service Bindings are not cached automatically, you need to call the Cache API manually

Ryley•6/20/24, 10:34 AM

Hey there. Is it safe to publish wrangler.toml file for public repos. It has db id. What do you recommned??

RRyley Hey there. Is it safe to publish wrangler.toml file for public repos. It has db ...

Erisa•6/20/24, 10:35 AM

Database IDs, account IDs, etc. are all safe to publish. The ID is meaningless unless you have access to the account or are a Cloudflare employee. You can see opensource repos published by Cloudflare with IDs in wrangler.toml

EErisa Database IDs, account IDs, etc. are all safe to publish. The ID is meaningless u...

Ryley•6/20/24, 10:36 AM

Thank you.

Dmitry•6/20/24, 12:15 PM

Lol.. how many times do I have to complete the "Quick Start Guide' .. it literally pops up 3 times a day (even after i've completed it each time) :pepe_mad:

Dmitry•6/20/24, 12:15 PM

Ya'll killing me Cloudflare :kekw:

lupin•6/20/24, 2:34 PM

Any CF engineer that could help on this matter ?:

workers-and-pages-helpDeploying with keep-vars not working anymore

This broke several prod pipelines and we still didn't find the root cause since we didn't change anything on our side :thisisfinefire:

Cheers !

MISANTHROPIC J•6/20/24, 6:18 PM

Hi all! Noob here, sorry if this is a silly question, but I'm not finding clear answers. Are workers only able to be deployed on the dev urls created by cloudflare on a free plan ?

Context: I'm trying to set up a reverse proxy worker for dispenseapp so my dispense store url is "mydomain.com/store" the documentation on dispenseapp seems straightforward and even updates code automatically when updating desired store url or adding multiple stores. After setting up everything step by step it works fine on the dev url, but the route pointed at my domain doesn't work at all. I feel like I'm missing a critical step to connect this worker to my domain on cloudflare besides setting up my

route : domain.com/shop*

Zone: domain

Xiao 🥑•6/20/24, 9:14 PM

Hi question about the workers execution time

I'm migrating from Supabase edge function cause they have a hard limit on the function execution time (2 seconds), does anyone know what is the limitation on Workers?
I'm trying to generate a pdf which contains ~30 pages, which could take ~10s.

XXiao 🥑Hi question about the workers execution time I'm migrating from Supabase edge f...

ChaikaOP•6/20/24, 9:18 PM

there's no hard limit on duration (other then the fact that runtime upgrades happen and your worker only gets 30s to finish its work). There are limits on CPU Time (time the cpu is active/doing stuff, most importantly excludes time waiting on i/o like fetchs) and Memory: https://developers.cloudflare.com/workers/platform/limits/#worker-limits

Cloudflare Docs

Limits · Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

CChaika there's no hard limit on duration (other then the fact that runtime upgrades hap...

Xiao 🥑•6/20/24, 9:19 PM

that's exactly what I'm looking for, thanks so much :MeowHeartCloudflare:

taczzy•6/20/24, 10:55 PM

In https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler, under the "What’s next for the convergence of Workers and Pages?" there is a bit about Pages features coming soon to Workers - Serve static assets from Workers. You will be able to deploy and serve static assets as part of Workers – just like you can with Pages today – and build Workers using full-stack frameworks!

I'm curious, are there any new updates on this work?

Walshy•6/21/24, 8:27 AM

Just that it's in development and we're working on it

ItsWendell•6/21/24, 9:37 AM

In Cloudflare (Workers), how does the 'fetch' caching behavoir work when the fetched resource is a redirected to somewhere else?

Let's say we have a cache everything and TTL on a specific fetch request, that fetch requests ends up doing a temporary redirect to another URL, will it, the URL that is being redirected to, be fetched from cloudflare's cache if available?

A concrete example for our Storyblok scenario: If we don't have a cache version (cv) available and we fetch

/v2/cdn/stories/home?key=234234234

/v2/cdn/stories/home?key=234234234

, Storyblok will redirect this to a link that does have the cache value (cv) query param

/v2/cdn/stories/home?cv=2342342234&key=234234234

/v2/cdn/stories/home?cv=2342342234&key=234234234

, will the second URL be fetched from the cloudflare cache or not? Preferably in this case, if we get a redirect status code from Storyblok, we don't want to cache that response. But if it redirects to an URL that does have the cache version (cv) included, and we already have that cached, we want to actually retrieve it from the cloudflare cache if available there.

Might I need to add a response status code specific cache rule? Or how does the caching behavoir work when redirects are involved?

Xiao 🥑•6/21/24, 1:40 PM

Hi I'm to create a simple api with itty-router, but ran into this error, anyone has any idea how to fix this?

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

const router = Router();

router.get('/api', () => {
    return new Response('Welcome to the inspecti api', {
            headers: { 'Content-Type': 'text/plain' },
    });
});

router.all('*', () => new Response('404, not found!', { status: 404 }));

export default {
    fetch: (request: Request, env: Env, ctx: ExecutionContext) => router.handle(request, env, ctx),
} satisfies ExportedHandler<Env>;

const router = Router();

router.get('/api', () => {
    return new Response('Welcome to the inspecti api', {
            headers: { 'Content-Type': 'text/plain' },
    });
});

router.all('*', () => new Response('404, not found!', { status: 404 }));

export default {
    fetch: (request: Request, env: Env, ctx: ExecutionContext) => router.handle(request, env, ctx),
} satisfies ExportedHandler<Env>;

SonyC•6/21/24, 3:19 PM

Good day guys.
I wanna ask for advices about how deploy a worker API that I implemented using D1 as storage and a react SPA built using vite, that I used to serve using express.js.
1 - Is it good to deploy the worker as is and in parallel the react SPA in pages? Will this be ok?
2- Will this need cors whitelist or something?
3 -Will be better to serve the SPA using getAssetFromKV from '@Cloudflare/kv-asset-handler'?
4- Will using functions will be better for my case?

I'm reading now about Workers Sites, will this be an option?

dave•6/21/24, 7:38 PM

YES YES YES https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata/

Cloudflare Docs

Version metadata · Cloudflare Workers docs

Exposes Worker version metadata (

versionID

versionID

and

versionTag

versionTag

). These fields can be added to events emitted from the Worker to send to downstream …

dave•6/21/24, 7:38 PM

finally

skoogeer•6/21/24, 8:56 PM

Hi Everyone. Existing Cloudflare Workers customers can now maintain free access to the MailChannels sending API. All we ask for is for you to help us guide product improvements. If you want a free API key and console account that will continue working after June 30th, please DM me and I will hook you up. Official notice: https://support.mailchannels.com/hc/en-us/articles/26814255454093-End-of-Life-Notice-Cloudflare-Workers

skoogeer•6/21/24, 8:56 PM

PS If I'm slow to reply, feel free to fill in our sales contact form: https://info.mailchannels.com/contact-sales

Contact Sales

Contact MailChannels to learn more about how we can help secure and deliver your hosting emails.

James•6/21/24, 9:03 PM

yeah I would definitely recommend folks just stick with Resend, Postmark, SendGrid, SES, or many others rather than using MailChannels. Security issues and the company's communication has made it impossible for me to recommend MailChannels to anyone. See https://community.cloudflare.com/t/mailchannels-end-of-life-notice-migrate-now/658638#alternatives-1 for some links to tutorials for alternatives.

Sskoogeer Hi Everyone. Existing Cloudflare Workers customers can now maintain free access ...

James•6/21/24, 9:19 PM

In exchange for being an early user, you will receive a significantly discounted price when the improved commercial service launches later this year.

Can you clarify this? Will the API key you get after DMing you not actually remain free and "continue working"?

skoogeer•6/21/24, 9:28 PM

The API will continue working. We have been providing email delivery service continuously since 2012 and have no intention to pull any rugs. The only thing that is ending is the provision of a free service tied to Workers IPs.

JJames yeah I would definitely recommend folks just stick with Resend, Postmark, SendGr...

dave•6/21/24, 9:32 PM

+9,000, AWS SES is so much better.

const router = Router(); router.get('/api', () => { return new Response('Welcome to the inspecti api', { headers: { 'Content-Type': 'text/plain' }, }); }); router.all('*', () => new Response('404, not found!', { status: 404 })); export default { fetch: (request: Request, env: Env, ctx: ExecutionContext) => router.handle(request, env, ctx), } satisfies ExportedHandler<Env>;

httpx/aiohttp are just patched to normal js fetch <https://github.com/cloudflare/workerd/blob/main/s

Similar Threads