i did exactly 100% same as the tutorial

Original message was deleted

0

0x146231489231923OP•11/10/24, 10:19 AM

let me try with your sample code

0

0x146231489231923OP•11/10/24, 10:20 AM

i saw someone discussed this in github

00x146231489231923 i did exactly 100% same as the tutorial

0

0x146231489231923OP•11/10/24, 10:21 AM

.

0

0x146231489231923OP•11/10/24, 10:22 AM

i created another file cron.ts, and pasted the same code, then i realised it was all wrong

0

0x146231489231923OP•11/10/24, 10:23 AM

even if i am using workers, this poor documentation doesnt specify where you should store your code

0

0x146231489231923OP•11/10/24, 10:23 AM

i would create a new file anyways by jumping into this documentation

0

0x146231489231923OP•11/10/24, 10:24 AM

0

0x146231489231923OP•11/10/24, 10:25 AM

which part mentioned it should be merged into the

index.ts

index.ts

or where should the file stored

0

0x146231489231923OP•11/10/24, 10:25 AM

why cant just admit poor documentation was maintained

0

0x146231489231923OP•11/10/24, 10:27 AM

ok thx for your input

0

0x146231489231923OP•11/10/24, 10:27 AM

i appreciate humbly

Original message was deleted

0

0x146231489231923OP•11/10/24, 10:27 AM

i forgot why i use hono at the beginning

0

0x146231489231923OP•11/10/24, 10:28 AM

dont u use hono or any framework

0

0x146231489231923OP•11/10/24, 10:34 AM

got it, thanks a lot

WWalshy What are you seeing?

O

Omar Abid•11/10/24, 11:41 AM

I lost the error message (will capture it next time) but was able to deploy after 30min or so.

J

jumpspace•11/10/24, 12:33 PM

Anyone familiar with cron jobs in workers? I created the scheduler and during the deVelopment when I make the curl req to the _scheduled route to check the working of the scheduler I am getting 404 error can anyone help with this.

here;s my code -
https://github.com/kirtirajsinh/philosopher-ai/blob/main/src/index.ts#L80

GitHub

philosopher-ai/src/index.ts at main · kirtirajsinh/philosopher-ai

Contribute to kirtirajsinh/philosopher-ai development by creating an account on GitHub.

Jjumpspace Anyone familiar with cron jobs in workers? I created the scheduler and during th...

0

0x146231489231923OP•11/10/24, 3:07 PM

exactly another victim like me

0

0x146231489231923OP•11/10/24, 3:08 PM

bro u have to put the schedule in your

index.ts

index.ts

, im sure you are doing

export default app

export default app

export default app

export default app right now

change to this

export default {
  fetch: app.fetch,
  async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext
  ) {
      ....
     }
}

export default {
  fetch: app.fetch,
  async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext
  ) {
      ....
     }
}

export default {
  fetch: app.fetch,
  async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext
  ) {
      ....
     }
}

export default {
  fetch: app.fetch,
  async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext
  ) {
      ....
     }
}

Original message was deleted

0

0x146231489231923OP•11/10/24, 3:08 PM

read this

Original message was deleted

0

0x146231489231923OP•11/10/24, 3:08 PM

and this

00x146231489231923 exactly another victim like me

J

jumpspace•11/10/24, 4:22 PM

do checkout my code I am exporting the scheduled function still when I try to make the curl request to check the scheduler I get 404 not found error

https://github.com/kirtirajsinh/philosopher-ai/blob/main/src/index.ts#L80

GitHub

philosopher-ai/src/index.ts at main · kirtirajsinh/philosopher-ai

Contribute to kirtirajsinh/philosopher-ai development by creating an account on GitHub.

J

jumpspace•11/10/24, 4:23 PM

@Leo

Y

Yomisana•11/10/24, 4:23 PM

Workers And Pages I create Nextjs SSR project and Workers and Pages not support else member to access?

Original message was deleted

J

jumpspace•11/10/24, 4:35 PM

yes

Jjumpspace do checkout my code I am exporting the scheduled function still when I try to ma...

0

0x146231489231923OP•11/10/24, 5:16 PM

i think your

scheduled

scheduled

should look like this ?

async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext,
  ) {
    console.log("cron processed");
  },

async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext,
  ) {
    console.log("cron processed");
  },

async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext,
  ) {
    console.log("cron processed");
  },

async scheduled(
    controller: ScheduledController,
    env: Env,
    ctx: ExecutionContext,
  ) {
    console.log("cron processed");
  },

why you creating a function in it

.

.gwapes•11/10/24, 5:19 PM

Because you can?

0

0x146231489231923OP•11/10/24, 5:35 PM

wow smartass

00x146231489231923 wow smartass

F

fry69•11/10/24, 5:38 PM

Please keep the discussion here friendly, if you want help.

..gwapes Because you can?

0

0x146231489231923OP•11/10/24, 5:39 PM

this isnt friendly either

00x146231489231923 this isnt friendly either 😆

F

fry69•11/10/24, 5:40 PM

Then ignore it. You are responsible for what you type here.

0

0x146231489231923OP•11/10/24, 5:41 PM

well then u should send him this

Please keep the discussion here friendly, if you want help.

Please keep the discussion here friendly, if you want help.

00x146231489231923 well then u should send him this `Please keep the discussion here friendly, if y...

F

fry69•11/10/24, 5:41 PM

Again. If you want help, stop fussing. If you think something needs moderation, call @Community Champion

0

0x146231489231923OP•11/10/24, 5:42 PM

you are the one fussing right here

0

0x146231489231923OP•11/10/24, 5:42 PM

whats wrong

00x146231489231923 wow smartass

D

DaniFoldi•11/10/24, 5:42 PM

Mind your language

0

0x146231489231923OP•11/10/24, 5:42 PM

because i can?

00x146231489231923 because i can?

I

Isaac McFadyen•11/10/24, 5:42 PM

Let's stop this entire discussion here, it's not productive and is getting to be uncivil.

..gwapes Because you can?

0

0x146231489231923OP•11/10/24, 5:42 PM

or because you can?

0

0x146231489231923OP•11/10/24, 5:43 PM

smh

B

BigDog911•11/10/24, 11:00 PM

Do you guys know what to make of “error:netdev is not set”

J

James•11/10/24, 11:39 PM

In what context? Can you share any more info and where you’re seeing this error?

S

sdil•11/11/24, 2:01 AM

Hi everyone. I'm evaluating Cloudflare Workers for my next project. I built a simple PoC using Hono, connecting to TursoDB and deployed to Cloudflare Workers using Smart placement.

I'm observing a very long TTFB on cold boots (up to 8s) and warm boots (up to 800ms, kinda deal breaker to me). Considering this is a very simple API that has no other logics other than querying a data with 1 row, is there is any way I can speed up the my workers? After they are warm, I can get around ~21ms latency.

Thanks in advance

JJames In what context? Can you share any more info and where you’re seeing this error?

B

BigDog911•11/11/24, 3:37 AM

I’ll probably make a post if I’m gonna give context.

Ssdil Hi everyone. I'm evaluating Cloudflare Workers for my next project. I built a si...

B

Brett Willis•11/11/24, 7:56 AM

Hard to say without seeing the project, but to eat up 8s it must be doing some initialisation with external API calls? Or is there some cold start or Turso's side related to accessing Turso from different regions (I haven't used Turso so I don't know how it operates).
From all my experience, I can reach workers on the far side of the world consistently around ~200ms, cold start or not.
So it could be related to doing some expensive (long running API request) initialisation on each worker request? If so, you could try firstly "caching" that initialisation in global variables so it is shared between requests to the same worker instance. And secondly caching initialisation responses locally in the datacentre using the Cache API so it can be retrieve very quickly even for a new worker instance.
However if your code is indeed just a "simple POC" with no such long running initialisation then I've got a feeling that the delay may be on Turso's API?

M

MrHebs•11/11/24, 12:46 PM

Does anyone have a recommended “pattern” for updating API shield schema validation during the deployment process of a Worker? Do you just upload a new version of the OpenAPI schema each time via API?

Interested to know what process (if any) others might use

J

jumpspace•11/11/24, 2:34 PM

anyone familiar with creating Dynamic image with honojs. I tried with svgs but on storing it on db it gets as a HTML Document (.svg) I want it directly as a png or jpg not any html document.

Sharp is one option for converting it but its not compatible with honojs. Any ideas on this?

BBrett Willis Hard to say without seeing the project, but to eat up 8s it must be doing some i...

S

sdil•11/11/24, 2:53 PM

i guess you're right. i quickly instrumented my app and saw Turso DB was slow for the first few initial requests. thanks @Brett Willis !

Jjumpspace anyone familiar with creating Dynamic image with honojs. I tried with svgs but o...

I

Isaac McFadyen•11/11/24, 6:40 PM

Sharp would be compatible with Hono, it just might not be compatible with Workers. Have you tried the Sharp WASM version?

IIsaac McFadyen Sharp would be compatible with Hono, it just might not be compatible with Worker...

J

jumpspace•11/11/24, 6:58 PM

I found one wasm based lib @resvg/resvg-wasm to convert from svg to png. but the issue with that is its not rendering the text. gettign a full empty image with just background

import { Resvg, ResvgRenderOptions, initWasm } from '@resvg/resvg-wasm';
import wasmModule from '@resvg/resvg-wasm/index_bg.wasm';


export const generateImage = async (text: string) => {

    console.log(text, "this is the text");



    const svg =

import { Resvg, ResvgRenderOptions, initWasm } from '@resvg/resvg-wasm';
import wasmModule from '@resvg/resvg-wasm/index_bg.wasm';


export const generateImage = async (text: string) => {

    console.log(text, "this is the text");



    const svg =

import { Resvg, ResvgRenderOptions, initWasm } from '@resvg/resvg-wasm';
import wasmModule from '@resvg/resvg-wasm/index_bg.wasm';


export const generateImage = async (text: string) => {

    console.log(text, "this is the text");



    const svg =

import { Resvg, ResvgRenderOptions, initWasm } from '@resvg/resvg-wasm';
import wasmModule from '@resvg/resvg-wasm/index_bg.wasm';


export const generateImage = async (text: string) => {

    console.log(text, "this is the text");



    const svg =

;


    try {
        await initWasm(wasmModule);

    } catch (error) {
        console.error('Resvg wasm not initialized');
        throw error;
    }


    const opts: ResvgRenderOptions = {
        background: "white", // Optional: set background color
        fitTo: {
            mode: "width",
            value: 600, // Adjust based on your needs
        },
        font: {
            loadSystemFonts: true, // Disable system fonts if you're using custom fonts
        },
    };


    const resvg = new Resvg(svg, opts);
    console.log(resvg, "this is the resvg");
    const pngData = resvg.render();

    const pngBuffer = pngData.asPng();

    return pngBuffer;

};

;


    try {
        await initWasm(wasmModule);

    } catch (error) {
        console.error('Resvg wasm not initialized');
        throw error;
    }


    const opts: ResvgRenderOptions = {
        background: "white", // Optional: set background color
        fitTo: {
            mode: "width",
            value: 600, // Adjust based on your needs
        },
        font: {
            loadSystemFonts: true, // Disable system fonts if you're using custom fonts
        },
    };


    const resvg = new Resvg(svg, opts);
    console.log(resvg, "this is the resvg");
    const pngData = resvg.render();

    const pngBuffer = pngData.asPng();

    return pngBuffer;

};

;


    try {
        await initWasm(wasmModule);

    } catch (error) {
        console.error('Resvg wasm not initialized');
        throw error;
    }


    const opts: ResvgRenderOptions = {
        background: "white", // Optional: set background color
        fitTo: {
            mode: "width",
            value: 600, // Adjust based on your needs
        },
        font: {
            loadSystemFonts: true, // Disable system fonts if you're using custom fonts
        },
    };


    const resvg = new Resvg(svg, opts);
    console.log(resvg, "this is the resvg");
    const pngData = resvg.render();

    const pngBuffer = pngData.asPng();

    return pngBuffer;

};

;


    try {
        await initWasm(wasmModule);

    } catch (error) {
        console.error('Resvg wasm not initialized');
        throw error;
    }


    const opts: ResvgRenderOptions = {
        background: "white", // Optional: set background color
        fitTo: {
            mode: "width",
            value: 600, // Adjust based on your needs
        },
        font: {
            loadSystemFonts: true, // Disable system fonts if you're using custom fonts
        },
    };


    const resvg = new Resvg(svg, opts);
    console.log(resvg, "this is the resvg");
    const pngData = resvg.render();

    const pngBuffer = pngData.asPng();

    return pngBuffer;

};

J

James•11/11/24, 7:48 PM

I would guess that the fonts being missing are your issue. You may need to bundle the fonts up yourself and then pass them in via

font: {
  fontsBuffers: [fontBuffer], //
},

font: {
  fontsBuffers: [fontBuffer], //
},

font: {
  fontsBuffers: [fontBuffer], //
},

font: {
  fontsBuffers: [fontBuffer], //
},

where

fontBuffer

fontBuffer

is a raw

ttf

ttf

i did exactly 100% same as the tutorial

Similar Threads

Similar Threads

Similar Threads