Cloudflare Developers•2y ago

Do I pay for CPU time during a setTimeout?

Ddave Do I pay for CPU time during a setTimeout?

Hello, I’m Allie!•8/8/24, 10:25 PM

Assuming that you aren’t running anything else, no

kunal•8/9/24, 12:57 AM

For folks using Hyperdrive: Do you create a connection globally (outside the bounds of a request) so it's reused for the worker lifetime, or are you creating a connection per-request? Any performance implications for doing one or the other?

Normally I would do the former, but all the docs suggest the latter, so not sure if there is something Hyperdrive specific to keep in mind

Kkunal For folks using Hyperdrive: Do you create a connection globally (outside the bou...

Isaac McFadyen•8/9/24, 1:20 AM

Hyperdrive keeps a connection pool warm outside of your Worker (kinda like PgBouncer) so that's why globally storing the connection isn't required.

Isaac McFadyen•8/9/24, 1:21 AM

Globally storing anything in Workers can cause issues when dealing with multiple requests happening at the same time, so if there's no real specific reason to (which there isn't with Hyperdrive) it's best just to reconnect.

CChaika the --persist-to flag can be used to override where that local state folder is

ItsWendell•8/9/24, 7:04 AM

This actually has been working fine for us for local development, though we rarely have actual concurrent writes locally but it works fine for KV / R2 / D1 and stuff.

IItsWendell This actually has been working fine for us for local development, though we rare...

iska•8/9/24, 9:03 AM

thanks god this flag exist , very much needed for local indeed

iska•8/9/24, 9:04 AM

one thing though that was not practical is the hash of the sqlite file in local state i had to dig deep in a github issue to understand i had to decode it

Iiska thanks god this flag exist , very much needed for local indeed

ItsWendell•8/9/24, 9:30 AM

This is more a nextjs thing than a next on pages thing fyi!

Iiska one thing though that was not practical is the hash of the sqlite file in local ...

ItsWendell•8/9/24, 9:31 AM

Not sure what you mean here, can you elaborate?

Jose Ramos•8/9/24, 3:18 PM

My structure looks like this
src/index.js
src/router/routes.js

index.js
addEventListener('fetch', (event) => {
event.respondWith(router.handle(event.request))
});

routes has:

import { Router } from 'itty-router';

// Create a new router
const router = Router()

/*
Our index route, a simple hello world.
/
router.get("/", () => {
return new Response("Hello, world! This is the root page of your Worker template.")
})

router.all("", () => new Response("404, not found!", { status: 404 }));

export default router;

everytime I execute dev i get [wrangler:inf] GET / 500 Internal Server Error (48ms)
[wrangler:inf] GET /favicon.ico 500 Internal Server Error (2ms)
A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.
X [ERROR] Uncaught (in response) Error: The script will never generate a response.

Jose Ramos•8/9/24, 3:19 PM

New to dev with workers

justaname•8/9/24, 10:52 PM

Odd question is there support for mono repos?

Jjustaname Odd question is there support for mono repos?

Hello, I’m Allie!•8/9/24, 11:05 PM

In Workers?

wrangler

wrangler

doesn’t care about the layout of your project, you just run it in the directory you want to interact with

justaname•8/9/24, 11:05 PM

Alright thank you for the quick response! Thought so just wanted to be sure

iska•8/10/24, 5:16 AM

w n 6

tbehrsin•8/10/24, 7:39 AM

Hey... I have an issue adding a new website to my free plan. It says I have unpaid invoices, which I don't. The issue has been ongoing for over a month waiting for support to respond. Ticket number #01007138.

tbehrsin•8/10/24, 7:42 AM

The error happens when selecting the free plan and it says "You cannot add or modify subscriptions or services until all invoices are paid. Download each "Unpaid" invoice on your Billing page and click the "Pay online" link within each invoice to fix your account (Code: 1323)". However on the Billing Page it lists all invoices as having been paid.

Flare•8/10/24, 8:09 AM

To contact Cloudflare Support about an issue, please visit the Support Portal and fill in the form on the portal. After submission, you will receive confirmation over email.

Some issues, such as Account or Billing related issues, cannot be solved by the community.
Any plan level (including Free plans) can open tickets for Account, Billing or Registrar ticket categories. Make sure to select the correct category to ensure it goes to the right place.
For more information on the methods by which you can contact Support for your plan level, see Contacting Cloudflare Support - Cloudflare Docs

Sscruz Click to see attachment

Isaac McFadyen•8/10/24, 2:45 PM

That error doesn't seem to be coming from Workers... they don't give a 404 like that. Is it possible something in your code is generating the 404?

Isaac McFadyen•8/10/24, 2:46 PM

Also note that you're using POST in VSCode while using GET in the browser.

CssAvenger•8/10/24, 8:41 PM

Hey guys sorry for being a noob but I just got to know about workers and wranglr CLI
I am not able to run server any help?

CCssAvenger Hey guys sorry for being a noob but I just got to know about workers and wranglr...

CssAvenger•8/10/24, 8:42 PM

I logged in, after using npm create cloudflare and not cant use local server.
Kindly help

Walshy•8/10/24, 8:49 PM

there's a known issue with windows starting wrangler dev - https://github.com/cloudflare/workers-sdk/issues/6260

seems like the answer is here: https://github.com/cloudflare/workers-sdk/issues/6260#issuecomment-2269022869

.gwapes•8/10/24, 9:47 PM

Does waitUntil “wait” until the response you return from the worker has went “out” if that makes sense?

..gwapes Does waitUntil “wait” until the response you return from the worker has went “ou...

Ashley•8/10/24, 10:36 PM

See: https://developers.cloudflare.com/workers/runtime-apis/context/#waituntil but typically it’s used to take action after a response has been sent (e.g. return a response, then do “more work” after - e.g. cache something, emit events etc)

Cloudflare Docs

Context (ctx) · Cloudflare Workers docs

The Context API in Cloudflare Workers, including waitUntil and passThroughOnException.