Thanks for the help but I think I'm struggling to be clear about my need. Queues are an option. But

D

D Trombett•12/12/24, 8:08 PM

rpc?

C

CanRau•12/12/24, 8:08 PM

sorry for crossposting

S

SuperHelpflare•12/12/24, 8:09 PM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

C

Cobra•12/12/24, 8:28 PM

I'm running into a problem similar to the one Bradley described (workers-and-pages-discussions) — generating PDFs is taking significantly longer (and generating significantly larger files) than expected with CF's Puppeteer, and there's currently no way to switch the headless mode to

chrome-headless-shell

chrome-headless-shell

chrome-headless-shell

chrome-headless-shell... the docs for

puppeteer.launch()

puppeteer.launch()

puppeteer.launch()

puppeteer.launch() incorrectly suggest you can pass a

PuppeteerLaunchOptions

PuppeteerLaunchOptions

PuppeteerLaunchOptions

PuppeteerLaunchOptions param, but that only works for

PuppeteerNode.launch()

PuppeteerNode.launch()

PuppeteerNode.launch()

PuppeteerNode.launch(), not

PuppeteerWorkers.launch()

PuppeteerWorkers.launch()

PuppeteerWorkers.launch()

PuppeteerWorkers.launch()

GitHub

puppeteer/docs/api/puppeteer.launch.md at main · cloudflare/puppeteer

Puppeteer Core fork that works with Cloudflare Browser Workers - cloudflare/puppeteer

MMitya Thanks for the help but I think I'm struggling to be clear about my need. Queues...

J

James•12/12/24, 8:35 PM

thats pretty much what queues are best for

C

Chill guy•12/13/24, 5:10 AM

to use cron trigger the scheduled function should be exported default in index.ts file?

C

Chill guy•12/13/24, 5:11 AM

i tried to placing the scheduled function in separate file but bot working as expected

CChill guy i tried to placing the scheduled function in separate file but bot working as ...

H

Hello, I’m Allie!•12/13/24, 5:18 AM

The actual code can be located anywhere you like, as long as it is exported in your

main

main

file. For example:

// scheduled.ts
async function scheduled(evt, env, ctx) {
  // Do some work
}
// index.ts
import { scheduled } from "./scheduled";
export default { scheduled };

// scheduled.ts
async function scheduled(evt, env, ctx) {
  // Do some work
}
// index.ts
import { scheduled } from "./scheduled";
export default { scheduled };

// scheduled.ts
async function scheduled(evt, env, ctx) {
  // Do some work
}
// index.ts
import { scheduled } from "./scheduled";
export default { scheduled };

// scheduled.ts
async function scheduled(evt, env, ctx) {
  // Do some work
}
// index.ts
import { scheduled } from "./scheduled";
export default { scheduled };

C

Chill guy•12/13/24, 5:25 AM

thanks. Got it

Original message was deleted

J

James•12/13/24, 4:10 PM

Do you have

@types/node

@types/node

@types/node

@types/node installed per chance? Or is something loading

webworker

webworker

webworker

webworker or other similar types? What file openes if you browse to that erroring type?

J

James•12/13/24, 4:44 PM

Can you share a full code snippet, with how

res

res

res

res is assigned?

C

Cobra•12/13/24, 9:55 PM

can anyone offer any insights regarding this: workers-and-pages-discussions ?

U

UB•12/14/24, 2:34 AM

If anyone wants to use sourcemaps with Sentry on CF workers:
Do a dry-run to a folder (such as ./dist), do your sourcemap injection and upload on that, then deploy that dry ran file

As an example:

wrangler deploy --dry-run --outdir ./dist --minify
sentry-cli sourcemaps inject ./dist && sentry-cli sourcemaps upload ./dist
wrangler deploy --outdir ./dist --no-bundle ./dist/index.js

wrangler deploy --dry-run --outdir ./dist --minify
sentry-cli sourcemaps inject ./dist && sentry-cli sourcemaps upload ./dist
wrangler deploy --outdir ./dist --no-bundle ./dist/index.js

wrangler deploy --dry-run --outdir ./dist --minify
sentry-cli sourcemaps inject ./dist && sentry-cli sourcemaps upload ./dist
wrangler deploy --outdir ./dist --no-bundle ./dist/index.js

wrangler deploy --dry-run --outdir ./dist --minify
sentry-cli sourcemaps inject ./dist && sentry-cli sourcemaps upload ./dist
wrangler deploy --outdir ./dist --no-bundle ./dist/index.js

U

UB•12/14/24, 2:35 AM

Posting this because I spent more time than I'd like to admit on that

S

samsung•12/14/24, 5:01 AM

can anyone know what the price model "Cache using fetch" ?

Ssamsung can anyone know what the price model "Cache using fetch" ?

H

Hello, I’m Allie!•12/14/24, 5:25 AM

Free

S

samsung•12/14/24, 6:26 AM

with custom "cache key" in worker ? is free ?

Ssamsung with custom "cache key" in worker ? is free ?

H

Hello, I’m Allie!•12/14/24, 6:30 AM

Yes, that’s free

A

Aster•12/14/24, 6:36 AM

Hello

do you know if it is possible, using a cloudflare tunnel, to send HTTP requests from a web server running on a VPS to a cloudflare worker without exposing the worker endpoint publicly?

so:

Worker private endpoint <-> tunnel <-> web server somewhere (k8s, vps)

S

samsung•12/14/24, 6:42 AM

Requests to static assets are free and unlimited. https://developers.cloudflare.com/workers/platform/pricing/ but this is not static assest.

Cloudflare Docs

Pricing · Cloudflare Workers docs

Workers plans and pricing information.

S

samsung•12/14/24, 6:45 AM

fetch(event.request, { cf: { cacheKey: "some-string" } }); with cacheTtl

A

Ashley•12/14/24, 1:31 PM

Has anyone had any success passing large files from a Worker to an RPC Entrypoint? I tried passing the File itself and it errors (

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: from the client - doesn't even hit the RPC endpoint)

Then I tried passing the arrayBuffer - this works, but there are limits on RPC method calls of 1MiB so that naturally isn't going to work. I tried passing a ReadableStream (file.stream()) and it is passed, and is close, but then I get

Uncaught (in promise) TypeError: Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)

Uncaught (in promise) TypeError: Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)

Uncaught (in promise) TypeError: Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)

Uncaught (in promise) TypeError: Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)

And while it is a ReadableStream, it has no length for whatever reason (it seems to go from being a non-BYOB to a BYOB and length is undefined). Probably some JS-specifics I'm missing, anyone got any ideas?

J

johtso•12/14/24, 4:23 PM

I've suddenly started getting

The uploaded script has no registered event handlers. [code: 10068]

The uploaded script has no registered event handlers. [code: 10068]

The uploaded script has no registered event handlers. [code: 10068]

The uploaded script has no registered event handlers. [code: 10068], I don't think I've changed anything that would cause this.. any ideas how I could figure out what's going on?

J

johtso•12/14/24, 4:28 PM

my worker

export default

export default

export default

export defaults an object with a fetch handler, I don't see why this error would start appearing

J

johtso•12/14/24, 4:29 PM

I do also see

A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed

A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed

A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed

A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed

J

johtso•12/14/24, 5:10 PM

when running wrangler dev i get "service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.", but that makes no sense to me either

J

johtso•12/14/24, 5:14 PM

some kind of circular dependency?

D

D Trombett•12/14/24, 5:22 PM

Not sure if it's a bug or what but do you have a top-level await? What are your imports?

J

johtso•12/14/24, 5:27 PM

No, I shouldn't have a top level await, I have quite a few imports..

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

J

johtso•12/14/24, 5:27 PM

I guess I'll start stripping things away one by one..

D

D Trombett•12/14/24, 6:32 PM

I honestly have no idea how would you debug such error because I've had it too in the past and it is a pain but are you sure you don't have other logs before it?

DD Trombett I honestly have no idea how would you debug such error because I've had it too i...

J

johtso•12/14/24, 6:35 PM

all I get is

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

when running

workers dev

workers dev

workers dev

workers dev

J

johtso•12/14/24, 6:36 PM

when trying to deploy I get

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

Jjohtso when trying to deploy I get ``` ✘ [ERROR] A request to the Cloudflare API (/acco...

D

D Trombett•12/14/24, 6:46 PM

Uh, wait, does Cloudflare use commonjs in production? It's strange that you don't get the same error

J

johtso•12/14/24, 7:26 PM

ok, finally found the culprit after a whole day of commenting out code

J

johtso•12/14/24, 7:26 PM

and yes, it was a top level await that I'd added while testing things

J

johtso•12/14/24, 7:26 PM

I wonder if there's a more efficient way to find the offending code in a situation like this?

Jjohtso I wonder if there's a more efficient way to find the offending code in a situati...

H

Hello, I’m Allie!•12/14/24, 7:36 PM

A linter rule maybe?

J

johtso•12/14/24, 7:36 PM

yeah, I definitely need to set up some linting and typescript error checking for this project

J

johtso•12/14/24, 7:37 PM

also a lesson to commit early and often, the smaller the diff between your last working version and your current code, the less places there are for a new issue to hide and the fewer potential red herrings

J

johtso•12/14/24, 7:38 PM

don't do a big dependency update and write some new code without committing in between

M

MrBithles•12/15/24, 8:02 AM

For a local worker with remote flag that is setup with RPC (WorkerEntrypoint) and using browser render with queues is it possible to call worker's fetch locally because I only get 500 response and no logs to why. (Need to have remote flag because browser render doesn't work on local wrangler)

Worker code snippet

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

Calling worker via localhost

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

Logs from wrangler dev, but I don't see my console log in fetch

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

SShayan I have a CRON worker (Worker A) that fetches my database and gets a list of ID's...

H

Hello, I’m Allie!•12/15/24, 7:35 PM

You can use a Service Binding instead of fetching.

Cloudflare Docs

Service bindings - Runtime APIs · Cloudflare Workers docs

Facilitate Worker-to-Worker communication.

W

Walshy•12/15/24, 10:32 PM

https://en.m.wikipedia.org/wiki/CPU_time
tldr is that its compute time. If you're waiting for a fetch call for example, that is not counted.

W

Walshy•12/16/24, 12:43 AM

Yes

Thanks for the help but I think I'm struggling to be clear about my need. Queues are an option. But

Similar Threads

Similar Threads

Similar Threads