Another worker is the client that connects to a durable object that acts as the server. Basically I'

IIsak Another worker is the client that connects to a durable object that acts as the ...

H

Hello, I’m Allie!•5/16/24, 9:02 AM

Client Pricing: One Request per invocation, plus any CPU Time you consume

H

Hello, I’m Allie!•5/16/24, 9:03 AM

But only while processing. Keeping the WS open shouldn't be billed, though note that after about 30s you aren't guaranteed it won't be evicted

J

James Flores•5/17/24, 1:36 AM

Hello Cloudflare lovers! I just wanted to share a little worker snippet that I'm using to display a book cover given a title and author. It helps me display book covers for over 20k books without having to upload any images! https://gist.github.com/jamesflores/85e9777d5ca076b2d29312a31754003e

Gist

Cloudflare worker that returns a book cover given a book title and ...

Cloudflare worker that returns a book cover given a book title and author name using the Open Library API - worker.js

N

neoney•5/17/24, 9:11 AM

:woe: why

N

neoney•5/17/24, 9:12 AM

its nice to avoid callback hell

N

neoney•5/17/24, 9:14 AM

and to conditionally enter

N

neoney•5/17/24, 9:16 AM

hmm i see the reason for not implementing is just that its complicated and error prone

N

neoney•5/17/24, 9:16 AM

¯\_(ツ)_/¯

N

neoney•5/17/24, 9:16 AM

i guess ill have to do that

N

neoney•5/17/24, 9:41 AM

I guess I can use this as an alternative to that weird code to make it a bit simpler

export function withChildLogger<T>(
  bindings: Bindings,
  fn: (logger: Logger | undefined) => T,
  options?: ChildLoggerOptions,
): T {
  const logger = getLogger()?.child(bindings, options);

  return logger ? loggerStorage.run(logger, () => fn(logger)) : fn(logger);
}

export function withChildLogger<T>(
  bindings: Bindings,
  fn: (logger: Logger | undefined) => T,
  options?: ChildLoggerOptions,
): T {
  const logger = getLogger()?.child(bindings, options);

  return logger ? loggerStorage.run(logger, () => fn(logger)) : fn(logger);
}

export function withChildLogger<T>(
  bindings: Bindings,
  fn: (logger: Logger | undefined) => T,
  options?: ChildLoggerOptions,
): T {
  const logger = getLogger()?.child(bindings, options);

  return logger ? loggerStorage.run(logger, () => fn(logger)) : fn(logger);
}

export function withChildLogger<T>(
  bindings: Bindings,
  fn: (logger: Logger | undefined) => T,
  options?: ChildLoggerOptions,
): T {
  const logger = getLogger()?.child(bindings, options);

  return logger ? loggerStorage.run(logger, () => fn(logger)) : fn(logger);
}

A

avogadro•5/17/24, 12:48 PM

I am uploading a worker using

wrangler deploy

wrangler deploy

and getting this error

  workers.api.error.unknown [code: 10013]

workers.api.error.unknown [code: 10013]

  workers.api.error.unknown [code: 10013]

workers.api.error.unknown [code: 10013]. If I remove

upload_source_maps = true

upload_source_maps = true

upload_source_maps = true

upload_source_maps = true from wrangler.toml it starts working correctly. This used to be working before.
Are there any issues with source maps uploads right now?

W

Walshy•5/17/24, 1:18 PM

cc: @Nevi | Product Manager

A

avogadro•5/17/24, 1:28 PM

I just checked the above and this is not limited to just one worker, its affecting all of our worker deploys. Same symptom, commenting out the

upload_source_maps

upload_source_maps

upload_source_maps

upload_source_maps makes the upload work.

W

Walshy•5/17/24, 1:31 PM

Raised up to support so they can ping eng

W

Walshy•5/17/24, 2:55 PM

Incident opened - https://www.cloudflarestatus.com/incidents/8h32p5y03rrr

Cloudflare Workers API Errors

Aavogadro I am uploading a worker using `wrangler deploy` and getting this error ` worker...

A

avogadro•5/18/24, 2:41 PM

This error is back again (It was back to working yesterday).

Aavogadro This error is back again (It was back to working yesterday).

D

DaniFoldi•5/18/24, 2:49 PM

Let me try and repro

D

DaniFoldi•5/18/24, 2:50 PM

can repro, let me raise

S

safah222•5/18/24, 3:41 PM

Hello

S

safah222•5/18/24, 3:41 PM

How I can trigger WAF rule based on operation system ?? so if i want to block linux for example how I can trigger that

Ssafah222 How I can trigger WAF rule based on operation system ?? so if i want to block li...

A

arch•5/18/24, 3:49 PM

Short version - you can't. If you're relying on the User Agent, those can easily be changed. (I'd also generally discourage blocking based on a users OS)

S

safah222•5/18/24, 3:55 PM

how I can block based on user OS ??

Z

zegevlier•5/18/24, 4:12 PM

Look one message up, Arch answered you.

Aavogadro This error is back again (It was back to working yesterday).

D

DaniFoldi•5/18/24, 5:09 PM

This should be fixed now

S

sherlock•5/18/24, 7:18 PM

Hi! I'm working on a discord bot that i'm running on workers. The same code executed locally works, but on a worker it gets a CANCELED outcome and I'm struggling to understand why. There's a not of helpful info attached to it, nor am I abel to find any documentation related to it.
What causes the outcome to be CANCELED?

K

kaneki•5/18/24, 7:19 PM

Hello people, Where to share my open-source project related to workers?

Ssherlock Hi! I'm working on a discord bot that i'm running on workers. The same code exec...

K

kian•5/18/24, 7:19 PM

Are you using Service Bindings?

Kkaneki Hello people, Where to share my open-source project related to workers? 😅

K

kian•5/18/24, 7:19 PM

#what-i-built

Kkian #what-i-built

K

kaneki•5/18/24, 7:19 PM

Yayy thankss

Kkian Are you using Service Bindings?

S

sherlock•5/18/24, 7:20 PM

I have 2 KV bindings.
EDIT: just educated myself - no, not using any service bindings, but making a few API calls to discord in the lifetime of the request

Ssherlock I have 2 KV bindings. EDIT: just educated myself - no, not using any service bin...

S

sherlock•5/18/24, 8:30 PM

I think I found out why - I added some waits to retry the rate limited calls, and that increases my CPU time way beyond the free limit of 10ms. (Not the ideal way to do it, I know. I'm exploring Workers so this is fun

)

U

Unsmart•5/18/24, 8:41 PM

A wait/setTimeout doesnt use CPU time, what does use CPU time is parsing the data from KV (or from the discord api) so the larger the value the more CPU time it uses. Local dev doesnt have any CPU limits thus it works fine no matter the size

U

Unsmart•5/18/24, 8:42 PM

And KV doesnt really have rate limits so I highly doubt the calls to KV are ever being retried but the 1st call will succeed

S

sherlock•5/18/24, 8:45 PM

My calls are to a third party api, some manipulation on the data and then create a thread and post multiple messages on that thread. But as you say, IO wait time would be different from CPU time, so I'm back to square one, on why the request gets cancelled before I return a response :/

W

Walshy•5/18/24, 9:17 PM

also canceled is not due to cpu limits

W

Walshy•5/18/24, 9:17 PM

canceled means the client cancelled the request

W

Walshy•5/18/24, 9:17 PM

so your Worker took too long to respond and the request was cancelled

W

Walshy•5/18/24, 9:17 PM

if you're using interactions, they have a pretty fixed time to respond unless you defer

W

Walshy•5/18/24, 9:18 PM

waiting for these apis and things all add to that wall time limit imposed on you

W

Walshy•5/18/24, 9:18 PM

i'd recommend deferring and responding when you can

Kkian .dev.vars is just for local development

B

Baran•5/18/24, 9:28 PM

can I not add secrets in

.dev.vars

.dev.vars

file to

wrangler.toml

wrangler.toml

?

Something like this:

name = "TBA"
compatibility_date = "2024-05-12"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

[vars]
TURSO_DATABASE_URL = "libsql://TBA.turso.io"
TURSO_AUTH_TOKEN = "TBA"

[.dev.vars]
TURSO_DATABASE_URL = "http://127.0.0.1:8080"
TURSO_AUTH_TOKEN = "TBA"

name = "TBA"
compatibility_date = "2024-05-12"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

[vars]
TURSO_DATABASE_URL = "libsql://TBA.turso.io"
TURSO_AUTH_TOKEN = "TBA"

[.dev.vars]
TURSO_DATABASE_URL = "http://127.0.0.1:8080"
TURSO_AUTH_TOKEN = "TBA"

name = "TBA"
compatibility_date = "2024-05-12"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

[vars]
TURSO_DATABASE_URL = "libsql://TBA.turso.io"
TURSO_AUTH_TOKEN = "TBA"

[.dev.vars]
TURSO_DATABASE_URL = "http://127.0.0.1:8080"
TURSO_AUTH_TOKEN = "TBA"

name = "TBA"
compatibility_date = "2024-05-12"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

[vars]
TURSO_DATABASE_URL = "libsql://TBA.turso.io"
TURSO_AUTH_TOKEN = "TBA"

[.dev.vars]
TURSO_DATABASE_URL = "http://127.0.0.1:8080"
TURSO_AUTH_TOKEN = "TBA"

K

kian•5/18/24, 9:28 PM

[vars]

[vars]

[vars]

[vars] shouldn't contain secrets.

B

Baran•5/18/24, 9:29 PM

why?

K

kian•5/18/24, 9:29 PM

Because that's what secrets are for. They can't be seen in the dashboard and aren't in files that you commit to VCS (like Wrangler.toml)

K

kian•5/18/24, 9:30 PM

It's a shouldn't, not a can't - if you really want to you can but it isn't best practice.

B

Baran•5/18/24, 9:30 PM

so what is the alternative?

Another worker is the client that connects to a durable object that acts as the server. Basically I'

Similar Threads

Similar Threads

Similar Threads