Cloudflare Developers•9mo ago

https://github.com/keerthanenr/damp-violet-825c

GitHub

GitHub - keerthanenr/damp-violet-825c

Contribute to keerthanenr/damp-violet-825c development by creating an account on GitHub.

keerthOP•4/20/25, 7:57 PM

here's the repo for it

keerthOP•4/20/25, 7:57 PM

if anyone can see anything that could be causing this would appreciate it!

CChaika generally it's because you're leaking promises/async stuff across requests in th...

st3fan•4/20/25, 8:00 PM

I think my code is fine. I'm starting to think it is octokit that doesn't work well on Workers.

Kkeerth if anyone can see anything that could be causing this would appreciate it!

Chaika•4/20/25, 8:00 PM

bump your compat date back to 2025-03-31

Chaika•4/20/25, 8:01 PM

could be the new spa behavior is messing with stuff, easy thing to test
edit: looking at your code, you're trying to handle the *.js files, you'd need to enable your worker running of the assets ahead for that to work, if they're exact matches, your user worker won't be ran

Chaika•4/20/25, 8:01 PM

does it work in wrangler dev?

st3fan•4/20/25, 8:02 PM

worker secrets don't work for me unfortunately .. i set them with wrangler secret putwrangler secret put but they are empty in my app. I have an export interface Env { FOO_SECRET: string; }export interface Env { FOO_SECRET: string; } in my app but the string is empty.

st3fan•4/20/25, 8:05 PM

(i'm a noob and i accept some starting up pain but some of this stuf is ... uugghhh why are simple things so hard)

Sst3fan worker secrets don't work for me unfortunately .. i set them with `wrangler secr...

Chaika•4/20/25, 8:06 PM

if you're using local dev (the default of

wrangler dev

wrangler dev

), those secrets won't be pulled down, need to define them for local dev in .dev.vars file at the root of your project: https://developers.cloudflare.com/workers/configuration/secrets/#local-development-with-secrets

Cloudflare Docs

Secrets · Cloudflare Workers docs

Store sensitive information, like API keys and auth tokens, in your Worker.

CChaika does it work in wrangler dev?

keerthOP•4/20/25, 8:07 PM

yeah so after I tried to load the template in wrangler dev, it didn't work so I made those changes to try and make it work, will revert it back to the original code and make a small change to main.tsx

CChaika if you're using local dev (the default of `wrangler dev`), those secrets won't b...

st3fan•4/20/25, 8:09 PM

i am testing in production .. i think what may have gone wrong is that i assumed i had to add them to wrangler.jsonc as empty environment variables so that they are generated in the bindings/env .. but i think that may delete the secrets or override them .. from the docs is is unclear what the source of truth is

Sst3fan i am testing in production .. i think what may have gone wrong is that i assumed...

Chaika•4/20/25, 8:11 PM

yea that most likely cleared them. For everything but secrets the wrangler config local is the source of truth. It won't remove secrets if they're not present in there
https://developers.cloudflare.com/workers/wrangler/configuration/#source-of-truth

st3fan•4/20/25, 8:13 PM

so for secrets I need an

interface Env

interface Env

in my code that just lists those secrets .. but is that additive to the ones defines in wrangler.jsonc? I don't have any other bindings right now so i am not sure what happens next time in run

wrangler types

wrangler types

st3fan•4/20/25, 8:14 PM

i'll find out because now that this works i am going to iterate and turn this little github app into a Durable Object

Sst3fan so for secrets I need an `interface Env` in my code that just lists those secret...

Chaika•4/20/25, 8:15 PM

looks like it picks up secrets defined in .dev.vars wrangler types command with secrets

Chaika•4/20/25, 8:15 PM

I'm no big typescript guy and have never moved on from manually creating the env type lol

st3fan•4/20/25, 8:16 PM

(Re the "The script will never generate a response" error - i need to experiment a bit - i have a weird feeling that the retry logic in GitHub's octokit library may be the culprit - it may be the only thing that does something with timers or globals. My own code is all straightforward async/wait .. i read it a couple of times and can't find any odd cases that may leak promises or not return a Response.)

keerthOP•4/20/25, 8:19 PM

Decided to use a new vite react template below

https://github.com/keerthanenr/yellow-snow-7ffe
https://yellow-snow-7ffe.keerthanenr.workers.dev/

working as not edited

ut run npx wrangler dev

keerthOP•4/20/25, 8:20 PM

that's why in the the last repo implemented those fixes to try and fix the 404 issue

Kkeerth https://github.com/keerthanenr/damp-violet-825c

Chaika•4/20/25, 8:23 PM

I ran this template with npm run preview and npm run deploy and it just works

Chaika•4/20/25, 8:24 PM

it's setup to use vite in dev, not wrangler dev directly

keerthOP•4/20/25, 8:24 PM

just realised, it's my fault

keerthOP•4/20/25, 8:24 PM

all good had to set my node v20, I was on v18

keerthOP•4/20/25, 8:25 PM

didn't think it would be a big deal, apologises, but now it's set just fixed the issue

keerthOP•4/20/25, 8:25 PM

should've considered the warning properly, thanks so much checking, so works in dev and updated now

Wrekah•4/20/25, 9:05 PM

Hey Guys. I got static website, gatsbyjs + firebase setup. I am migrating over to cloudflare pages + d1.

Before, I was getting some static data from firestore during build time. From what I see, it is not that straightforward in cf pages from d1. I can:

get data with wrangler CLI before build
create Worker api and call it within build
perhaps use D1 rest API during build?

I am missing something here, is there anything easier?

usualdev•4/20/25, 10:43 PM

I think there is a bug with Hugo version in Pages. I'm following this guide https://developers.cloudflare.com/pages/framework-guides/deploy-a-hugo-site/#use-a-specific-or-newer-hugo-version

and added env variable:

HUGO_VERSION

HUGO_VERSION

0.146.6

0.146.6

But build logs are still showing the old version

hugo v0.118.2-da7983ac4b94d97d776d7c2405040de97e95c03d+extended linux/amd64 BuildDate=2023-08-31T11:23:51Z VendorInfo=gohugoio

hugo v0.118.2-da7983ac4b94d97d776d7c2405040de97e95c03d+extended linux/amd64 BuildDate=2023-08-31T11:23:51Z VendorInfo=gohugoio

The old (default version) is causing an error building the website, while locally it is building fine with no issues.

Uusualdev I think there is a bug with Hugo version in Pages. I'm following this guide http...

usualdev•4/20/25, 11:13 PM

An update, I tried setting

HUGO_VERSION

HUGO_VERSION

in a new project, and it worked fine. So I suppose this issue is only affecting current projects (already deployed websites)

st3fan•4/21/25, 1:21 AM

Am I supposed to

import { ExecutionContext, Request, Response } from '@cloudflare/workers-types';

import { ExecutionContext, Request, Response } from '@cloudflare/workers-types';

?

VSCode is happy now but

wrangler build

wrangler build

gives me ...

No matching export in
  "node_modules/@cloudflare/workers-types/index.ts" for import "Response"

No matching export in
  "node_modules/@cloudflare/workers-types/index.ts" for import "Response"

Even though the import is fine and there are no issues in the code. At least not according to the type checker.

st3fan•4/21/25, 2:32 AM

Sentry is nice. Also shows spans for things like http requests your worker makes. I just need to figure out how to upload the source map.

st3fan•4/21/25, 2:44 AM

Hmm

"upload_source_maps": true,

"upload_source_maps": true,

should probably be a default thing when you create a new worker project with typescript?

st3fan•4/21/25, 2:47 AM

THe "Using Sentry" link on the Integrations page is a 404 https://developers.cloudflare.com/workers/observability/sentry-integration

Cloudflare Docs

Sentry · Cloudflare Workers docs

Connect to a Sentry project from your Worker to automatically send errors and uncaught exceptions to Sentry.

st3fan•4/21/25, 2:48 AM

uhh that works but the link on the page doesn't

Kotkoroid•4/21/25, 9:48 AM

How do you deal with ids in wrangler config in public repos?

Kotkoroid•4/21/25, 9:50 AM

It's not a security risk whatsoever?

Воробушек UA•4/21/25, 10:36 AM

Hello, could someone please help...
When deploying a Nuxt on Cloudflare Pages, it seems that within a given deployment we can connect to Real‑time Logs: “View the console.log output and errors from your Functions.”
But I don’t see my console.log
I’m getting

{
  "wallTime": 32,
  "cpuTime": 24,
  "truncated": false,
  "executionModel": "stateless",
  "outcome": "ok",
  "scriptVersion": {
    "id": "10ab04ec-54b2-4d6e-ae80-9a74b49b3973"
  },
  "scriptName": "pages-worker--5948394-preview",
  "diagnosticsChannelEvents": [],
  "exceptions": [],
  "logs": [],
  ...

{
  "wallTime": 32,
  "cpuTime": 24,
  "truncated": false,
  "executionModel": "stateless",
  "outcome": "ok",
  "scriptVersion": {
    "id": "10ab04ec-54b2-4d6e-ae80-9a74b49b3973"
  },
  "scriptName": "pages-worker--5948394-preview",
  "diagnosticsChannelEvents": [],
  "exceptions": [],
  "logs": [],
  ...

I’d be very grateful if someone could point out what I’m doing wrong

SODaLC•4/21/25, 11:40 AM

Has anyone else had any luck adding a Queue Handler to an Astro Project? I've moved my project from Pages to a Worker and wanted to consolidate my Queue Worker into it but had no luck so far and there is no documentation on this either. Unless its still a pending feature?

James•4/21/25, 4:50 PM

There's no guarantee requests will hit the same Worker isolate, no. If you really need to do something that requires locks, you'll want to look at Durable Objects.

zegevlier•4/21/25, 4:57 PM

Where are you seeing that latency? Workers to DOs should not have that much

James•4/21/25, 5:01 PM

What's your use-case exactly where you're trying to prevent a race condition? I wonder if another Cloudflare product would make more sense here

James•4/21/25, 5:12 PM

Yeah DOs seem like the right call for this, but that latency seems very high. https://where.durableobjects.live/ is a great site that tracks this.

James•4/21/25, 5:17 PM

APAC definitely has fewer points where DOs are supported, but that latency still seems incredibly high to me

FFlikTeoh Yeah it was the initial connections I guess. Previously logging in through DO to...

Chaika•4/21/25, 5:19 PM

Inside of your durable object you can fetch https://cloudflare.com/cdn-cgi/trace and see

colo=

colo=

line for location, and you can visit /cdn-cgi/trace path of your worker to see where you're connecting to to run the worker, for debugging. Possible your DO is placed far away from you. If you don't pass any location hints, it should be created closest to the first request's colocation

zegevlier•4/21/25, 5:21 PM

Even from eg. ADL (Adelaide, Australia) to eeur is only 781ms, so 2/3 seconds is high even if it's very misplaced

{ "wallTime": 32, "cpuTime": 24, "truncated": false, "executionModel": "stateless", "outcome": "ok", "scriptVersion": { "id": "10ab04ec-54b2-4d6e-ae80-9a74b49b3973" }, "scriptName": "pages-worker--5948394-preview", "diagnosticsChannelEvents": [], "exceptions": [], "logs": [], ...

https://github.com/keerthanenr/damp-violet-825c

Similar Threads