it is by design. what is the ideal limit you're looking for?

W

WalshyOP•5/1/25, 1:02 PM

You could also use a message to put the env name in, we limit that to 100 chars

L

LordSilver•5/1/25, 6:37 PM

what's the diff between https://github.com/cloudflare/playwright-mcp and https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/browser-rendering ?

M

mr.niko.la•5/1/25, 7:43 PM

on paid plan, CPUexecution time is 30s?

i have a audio processing worker that uses 3rd party API to scribe 4-15s and i pipe the response to another llm api call that can take 8s all in one worker.

The dead times waiting for api are not counted only the cpu execution time?

how do i see workers total cpu usage time and memory usage time for each call.
I want to make sure my worker is not going to run out of time if i add more llm api cools on the same worker
thx

E

Ellie Rider•5/1/25, 8:03 PM

Question, is it possible to direct a path to a different host?

i.e. www.example.com proxies mywebsite.sample.com
but www.example.com/foo proxies foo.sample.com

E

Ellie Rider•5/1/25, 8:12 PM

OK thanks, I thought workers would have to be the way but I was hearing some conflicting ideas

M

mr.niko.la•5/1/25, 8:13 PM

maybe page rules could do it as well. i would ask grok/chatgpt

M

mr.niko.la•5/1/25, 8:14 PM

or dns settings if ur domain is with cf or whichever provider has dns

L

liam | helius.dev•5/1/25, 8:27 PM

Is the only way to get reliable websocket connections via DO's? We have lots of cases where websockets stop transmitting data with no error and support suggested setting up DO's. This is a problem though because DO's are not very scalable

Lliam | helius.dev Is the only way to get reliable websocket connections via DO's? We have lots of ...

H

Hard@Work•5/1/25, 9:06 PM

DOs are the way to make WebSockets survive an isolate restart, yeah. To make sure I understand, which part of DOs are you speaking about when you mention they aren't scalable?

S

Senti3ntB3ing•5/1/25, 9:11 PM

how do i call upon the secrets i set in the dashboard? docs only show how to set/delete them, not how to call upon them

SSenti3ntB3ing how do i call upon the secrets i set in the dashboard? docs only show how to set...

H

Hard@Work•5/1/25, 9:14 PM

What do you mean "call upon them"? Secrets are just present, like

export default class extends WorkerEntrypoint<Env> {
  fetch() {
    const mySecret = this.env.SOME_SECRET;
  }
}

export default class extends WorkerEntrypoint<Env> {
  fetch() {
    const mySecret = this.env.SOME_SECRET;
  }
}

export default class extends WorkerEntrypoint<Env> {
  fetch() {
    const mySecret = this.env.SOME_SECRET;
  }
}

export default class extends WorkerEntrypoint<Env> {
  fetch() {
    const mySecret = this.env.SOME_SECRET;
  }
}

S

Senti3ntB3ing•5/1/25, 9:22 PM

i don't have that section (or i couldn't find it) when i first started the project with wrangler

S

Senti3ntB3ing•5/1/25, 9:22 PM

i just had the

export default{.. fetch(req,env,ctx)

export default{.. fetch(req,env,ctx)

export default{.. fetch(req,env,ctx)

export default{.. fetch(req,env,ctx)

S

Senti3ntB3ing•5/1/25, 9:26 PM

import { Database } from "./database";

const TWITCH_APP_ID = await Database.get("twitch_app_id");
const TWITCH_APP_SECRET = await Database.get("twitch_app_secret");
const TWITCH_REFRESH = await Database.get("twitch_refresh_token");

const FIREBASE_SECRET = env.FIREBASE_SECRET

import { Database } from "./database";

const TWITCH_APP_ID = await Database.get("twitch_app_id");
const TWITCH_APP_SECRET = await Database.get("twitch_app_secret");
const TWITCH_REFRESH = await Database.get("twitch_refresh_token");

const FIREBASE_SECRET = env.FIREBASE_SECRET

import { Database } from "./database";

const TWITCH_APP_ID = await Database.get("twitch_app_id");
const TWITCH_APP_SECRET = await Database.get("twitch_app_secret");
const TWITCH_REFRESH = await Database.get("twitch_refresh_token");

const FIREBASE_SECRET = env.FIREBASE_SECRET

import { Database } from "./database";

const TWITCH_APP_ID = await Database.get("twitch_app_id");
const TWITCH_APP_SECRET = await Database.get("twitch_app_secret");
const TWITCH_REFRESH = await Database.get("twitch_refresh_token");

const FIREBASE_SECRET = env.FIREBASE_SECRET

i dont suppose this is how i would be calling upon the secret in question (FIREBASE_SECRET)

S

Senti3ntB3ing•5/1/25, 9:26 PM

or would i need to extend that default class?

SSenti3ntB3ing ```js import { Database } from "./database"; const TWITCH_APP_ID = await Datab...

H

Hard@Work•5/1/25, 9:26 PM

Yeah,

env.FIREBASE_SECRET

env.FIREBASE_SECRET

env.FIREBASE_SECRET

env.FIREBASE_SECRET should work

S

Senti3ntB3ing•5/1/25, 9:27 PM

thank you, it didn't generate a .env file and i know other runtimes have their own ways of calling secrets

HHard@Work DOs are the way to make WebSockets survive an isolate restart, yeah. To make sur...

L

liam | helius.dev•5/1/25, 9:58 PM

Why is it that workers hold zombie connections? It doesn't really make sense

DO requests/s is too low and creation of new DO is too slow

Lliam | helius.dev Why is it that workers hold zombie connections? It doesn't really make sense DO...

H

Hard@Work•5/1/25, 10:03 PM

Not sure I understand what you mean on the first part?

HHard@Work Not sure I understand what you mean on the first part?

L

liam | helius.dev•5/1/25, 10:05 PM

we frequently see that a websocket stays open, but data stops flowing. Something internal to CF is causing this and our support tickets have kept telling us to use DO's instead (which is also confusing because it requires so many extra layers/room for error when all we want is to proxy)

We've tested this extensively, removing CF solves the problem

S

Senti3ntB3ing•5/1/25, 10:23 PM

okay so i did some reading on the fetch handler - if i have a class object i have created to handle a whole bunch of API calls, and it uses fetch within itself, how can i make all of those fetch requests valid?

S

Senti3ntB3ing•5/1/25, 10:24 PM

would i wrap my whole class in

export default{
  async fetch(request){
    export class SomeClass{...

export default{
  async fetch(request){
    export class SomeClass{...

export default{
  async fetch(request){
    export class SomeClass{...

export default{
  async fetch(request){
    export class SomeClass{...

S

Senti3ntB3ing•5/1/25, 10:26 PM

so that every instance of the class calling

fetch

fetch

will be within the cloudflare fetch handler?

S

Senti3ntB3ing•5/1/25, 10:26 PM

or would i take each instance of me calling fetch and wrap the handler around those?