Is the only way to get reliable websocket connections via DO's? We have lots of cases where websocke

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)

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

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.devOP•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.devOP•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?

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

R

rufi•5/2/25, 3:10 AM

Currently when I deploy and tag it seems limited to 25 characters .
100 characters would be great.

S

Silvan•5/2/25, 9:27 AM

So trying to pass Headers from my sveltekit app to a rpc function i sadly get

DevalueError: Cannot stringify arbitrary non-POJOs

DevalueError: Cannot stringify arbitrary non-POJOs

is there a recommended way to serialize/deserialize them?

K

kerohije•5/2/25, 10:11 AM

Can this route setting be configured in wrangler's config file?

S

SteveIT•5/2/25, 11:15 AM

Anyone deploying gitbook to pages via the gitlab sync? Having trouble getting the build to succeed

S

Senti3ntB3ing•5/2/25, 2:06 PM

export default {
    async fetch(request, env, ctx) {

        const FIREBASE_SECRET = process.env.FIREBASE_SECRET;
        const FIREBASE_URL = process.env.FIREBASE_URL;
        console.log(FIREBASE_URL);

export default {
    async fetch(request, env, ctx) {

        const FIREBASE_SECRET = process.env.FIREBASE_SECRET;
        const FIREBASE_URL = process.env.FIREBASE_URL;
        console.log(FIREBASE_URL);

export default {
    async fetch(request, env, ctx) {

        const FIREBASE_SECRET = process.env.FIREBASE_SECRET;
        const FIREBASE_URL = process.env.FIREBASE_URL;
        console.log(FIREBASE_URL);

export default {
    async fetch(request, env, ctx) {

        const FIREBASE_SECRET = process.env.FIREBASE_SECRET;
        const FIREBASE_URL = process.env.FIREBASE_URL;
        console.log(FIREBASE_URL);

[wrangler:inf] GET / 304 Not Modified (9ms)
undefined
[wrangler:inf] GET /message 200 OK (15ms)

[wrangler:inf] GET / 304 Not Modified (9ms)
undefined
[wrangler:inf] GET /message 200 OK (15ms)

[wrangler:inf] GET / 304 Not Modified (9ms)
undefined
[wrangler:inf] GET /message 200 OK (15ms)

[wrangler:inf] GET / 304 Not Modified (9ms)
undefined
[wrangler:inf] GET /message 200 OK (15ms)

I don't understand why my secrets are coming in undefined

O

Ollie•5/2/25, 2:08 PM

You need to access them from env if l am correct

S

Senti3ntB3ing•5/2/25, 2:25 PM

how do i do that tho

S

Senti3ntB3ing•5/2/25, 2:26 PM

im using js not ts so i don't have access to the Env interface

SSenti3ntB3ing im using js not ts so i don't have access to the Env interface

H

Hello, I’m Allie!•5/2/25, 2:27 PM

You just do env.FIREBASE_SECRET

H

Hello, I’m Allie!•5/2/25, 2:27 PM

Whether TypeScript or JavaScript

S

Senti3ntB3ing•5/2/25, 2:30 PM

i've been doign that tho, it still shows up undefined

S

Senti3ntB3ing•5/2/25, 2:30 PM

i only recently changed it to process.env to try to get around it

O

Ollie•5/2/25, 2:31 PM

then its not set in your secrets, if you have not added it as a secret, then standard env vars get reset on each deploy (unless they are in your wrangler config file)

S

Senti3ntB3ing•5/2/25, 2:32 PM

i have them both set in wrangle.jsonc and set in my dashboard secrets, as well as thru npx wrangler secret put NAME

S

Senti3ntB3ing•5/2/25, 2:32 PM

none of the methods has let me use them

O

Ollie•5/2/25, 2:33 PM

maybe log out the entire