yeah so customers can deign functions and put htem up , a group of functions on our end may just be

R

robOP•5/22/23, 5:22 PM

like for a 'project' on our end

Rrob yeah so customers can deign functions and put htem up , a group of functions on ...

H

Hello, I’m Allie!•5/22/23, 6:25 PM

I would recommend bundling them all into a single Worker. That means less time is spent on routing them, and less of a cost to you if you pay per script

H

Hello, I’m Allie!•5/22/23, 6:26 PM

Other than increased size limits, there isn’t much of a benefit to splitting them up

R

robOP•5/22/23, 6:26 PM

jsut thinking ii ts like 5-6 functions await promisies if the executon time too long

I

Ivan Starkov•5/22/23, 7:00 PM

Seems like images resize on a worker for platform https://developers.cloudflare.com/images/image-resizing/resize-with-workers/ does’t work. Only through /cdn-cgi/image
Is it expected?

Resize with Cloudflare Workers · Cloudflare Image Optimization docs

Using Image Resizing with Workers gives you powerful programmatic control over every image request.

I

Ivan Starkov•5/22/23, 7:12 PM

Example of same worker deployed as ordinary worker
Everything is ok with resizing
https://check-image.wstd.work/cgi/image/IMG_0110_7HJWoMgorcaAyimP0XbQ7.jpeg?width=75&quality=80&format=auto

And as a worker for platform (not ok)
https://saas-test-b7wdc.wstd.work/cgi/image/IMG_0110_7HJWoMgorcaAyimP0XbQ7.jpeg?width=75&quality=80&format=auto

Resize code is +- same as in docs

I

Ivan Starkov•5/22/23, 7:27 PM

Not an issue, as I can easily resize images using dispatcher worker, just havent found this behavior is documented

S

sam•5/23/23, 1:44 AM

@tanushree could we request access? we just got into the workers launchpad program

S

sam•5/23/23, 1:44 AM

we previously were in via Dyme Cloud, which is now defunct

S

sam•5/23/23, 1:44 AM

yay startup pivots

IIvan Starkov Not an issue, as I can easily resize images using dispatcher worker, just havent...

T

tanushree │ Workers PM•5/24/23, 3:15 AM

You might be the first person to have tried this out! This is seems odd to me though, something for us to investigate

Ssam @tanushree could we request access? we just got into the workers launchpad progr...

T

tanushree │ Workers PM•5/24/23, 3:16 AM

Yes! DM me your Cloudflare account ID

Rrodrik Hi everyone, quick question around Workers for Platforms and Smart Placement: is...

T

tanushree │ Workers PM•5/24/23, 3:18 AM

Outbound Workers - need to confirm this. Is it configurable through API but will get back to you on how. What's your use case?

Eeidam hey, are the cpu and subrequests limit working already? subrequests do not seem ...

T

tanushree │ Workers PM•5/30/23, 5:24 PM

it should work! How do you have it defined in the dispatcher?

J

jman•5/31/23, 10:46 AM

to support user level cron triggers, I imagine implementing it with DO alarms would be the most straightforward path?

I just wanted to confirm there wasn't anything with the existing workers cron triggers functionality I was missing

I

Ivan Starkov•5/31/23, 4:54 PM

Just found that cloudflare worker types has following type for the DispatchNamespace

export interface DispatchNamespace {
  /**
   * @param name Name of the Worker script.
   * @param args Arguments to Worker script.
   * @param options Options for Dynamic Dispatch invocation.
   * @returns A Fetcher object that allows you to send requests to the Worker script.
   * @throws If the Worker script does not exist in this dispatch namespace, an error will be thrown.
   */
  get(
    name: string,
    args?: {
      [key: string]: any;
    },
    options?: DynamicDispatchOptions
  ): Fetcher;
}

export interface DispatchNamespace {
  /**
   * @param name Name of the Worker script.
   * @param args Arguments to Worker script.
   * @param options Options for Dynamic Dispatch invocation.
   * @returns A Fetcher object that allows you to send requests to the Worker script.
   * @throws If the Worker script does not exist in this dispatch namespace, an error will be thrown.
   */
  get(
    name: string,
    args?: {
      [key: string]: any;
    },
    options?: DynamicDispatchOptions
  ): Fetcher;
}

export interface DispatchNamespace {
  /**
   * @param name Name of the Worker script.
   * @param args Arguments to Worker script.
   * @param options Options for Dynamic Dispatch invocation.
   * @returns A Fetcher object that allows you to send requests to the Worker script.
   * @throws If the Worker script does not exist in this dispatch namespace, an error will be thrown.
   */
  get(
    name: string,
    args?: {
      [key: string]: any;
    },
    options?: DynamicDispatchOptions
  ): Fetcher;
}

export interface DispatchNamespace {
  /**
   * @param name Name of the Worker script.
   * @param args Arguments to Worker script.
   * @param options Options for Dynamic Dispatch invocation.
   * @returns A Fetcher object that allows you to send requests to the Worker script.
   * @throws If the Worker script does not exist in this dispatch namespace, an error will be thrown.
   */
  get(
    name: string,
    args?: {
      [key: string]: any;
    },
    options?: DynamicDispatchOptions
  ): Fetcher;
}

Interesting part here is

args

args

, does it documented somehow? How it can be used?

IIvan Starkov Just found that cloudflare worker types has following type for the DispatchName...

U

Unsmart•5/31/23, 4:56 PM

https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/platform/custom-limits/

Its for custom limits currently

Custom limits · Cloudflare for Platforms docs

Custom limits allow you to programmatically set limits on your customer’s Worker to set caps on usage. We support custom limits for CPU time and a …

Ttanushree │ Workers PM Second argument hasn't been implemented (publicly) yet. It's a way to pass bindi...

D

DaniFoldi•5/31/23, 4:56 PM

@istarkov this answers your question I believe

U

Unsmart•5/31/23, 4:56 PM

ah that one oops

I

Ivan Starkov•6/4/23, 5:26 AM

Getting "CNAME Cross-User Banned" using Cloudflare for Saas and r2 with custom domain.
We have:

r2 bucket with 2 custom domains https://developers.cloudflare.com/r2/buckets/public-buckets/#custom-domains-configuration
```
assets.webstudio.is
```
assets.webstudio.is
```
assets.webstudio.is
```
assets.webstudio.is
and
```
assets.wstd.work
```
assets.wstd.work
```
assets.wstd.work
```
assets.wstd.work
Worker as SaaS fallback origin https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/domain-support/worker-as-origin/ with dispatch namespace inside placed on route
```
*/*
```
*/*
```
*/*
```
*/*
at
```
wstd.work
```
wstd.work
```
wstd.work
```
wstd.work
zone
Worker route service for
```
assets.wstd.work/*
```
assets.wstd.work/*
```
assets.wstd.work/*
```
assets.wstd.work/*
is set to
```
None
```
None
```
None
```
None
to bypass
```
2
```
2
```
2
```
2
.
DNS Entries for SaaS with
```
proxy-fallback A  192.0.2.1
```
proxy-fallback A 192.0.2.1
```
proxy-fallback A  192.0.2.1
```
proxy-fallback A 192.0.2.1
```
*.customers CNAME proxy-fallback.wstd.work
```
*.customers CNAME proxy-fallback.wstd.work
```
*.customers CNAME proxy-fallback.wstd.work
```
*.customers CNAME proxy-fallback.wstd.work

Now if inside worker for SaaS fallback origin we have the following fetch

await fetch(`https://assets.wstd.work/some-resource.ext`, request);

await fetch(`https://assets.wstd.work/some-resource.ext`, request);

await fetch(`https://assets.wstd.work/some-resource.ext`, request);

await fetch(`https://assets.wstd.work/some-resource.ext`, request);

The fetch above fails with "CNAME Cross-User Banned" Error 1014

BUT if we change fetch onto

await fetch(`https://assets.webstudio.is/some-resource.ext`, request);

await fetch(`https://assets.webstudio.is/some-resource.ext`, request);

await fetch(`https://assets.webstudio.is/some-resource.ext`, request);

await fetch(`https://assets.webstudio.is/some-resource.ext`, request);

Everything is OK.

I think that its a bug, as both domains are on same account, we are using cloudflare for SaaS, and access to

assets.wstd.work

assets.wstd.work

assets.wstd.work

assets.wstd.work must not be prevented

Important detail, the fail is reproduced ONLY if customer domain is placed on cloudflare.
And has

PROXY

PROXY

PROXY

PROXY enabled on route.

So our customer with

poke-method.work

poke-method.work

poke-method.work

poke-method.work domain
Has DNS entry on Cloudflare

poke-method.work CNAME customer-id.customers.wstd.work

poke-method.work CNAME customer-id.customers.wstd.work

poke-method.work CNAME customer-id.customers.wstd.work

poke-method.work CNAME customer-id.customers.wstd.work with Proxy flag enabled

No issues with disabled Proxy flag, no issues with providers like Namecheap, only if customer provider is Cloudflare itself

IIvan Starkov Getting "CNAME Cross-User Banned" using Cloudflare for Saas and r2 with custom d...

U

Unsmart•6/4/23, 6:54 AM

I would recommend you put in a support ticket for that not really anything we can do in here about that

E

Erisa•6/4/23, 3:40 PM

There are some limitations around same-zone subrequests, this feels liike it might be one of them

Ttoinbis I'll try this channel, it seems closest to my question. I wonder who from Cloudf...

D

DaniFoldi•6/7/23, 7:19 AM

Apps aren't really maintained any more, see general-discussions so I'm not sure anyone would be "the right person"

Ttoinbis The way I read this notification is that new version is being cooked (from earli...

E

Erisa•6/7/23, 10:12 AM

Thats correct, and I highly encourage you to fill in the form about your needs/experience so it goes to the right people.
Failing that if you still need to get in touch, maybe @Vero

can connect with the right people

CCetin /⧸/ Elefunc <λ>We have been getting this error without any code changes on our end for the last...

E

Erisa•6/7/23, 7:31 PM

closing the loop here - https://www.cloudflarestatus.com/incidents/1mj9jch1tqf9

Workers KV returning 500 HTTP responses, affecting several components