you sent that ticket from your startup Enterprise account though right? You can already do anything,

CChaika you sent that ticket from your startup Enterprise account though right? You can ...

D

dave•1/4/24, 8:36 PM

correct. I also did ask a follow-up if this would apply if I was on a free or pro plan, will let ya know.

L

lukas•1/4/24, 10:02 PM

curious, what is a good way to store an access token? i was thinking using KV but that is not safe unless you hash the value

in-memory is only available for a period of time and that depends on where the worker is spawned in so it might not even have that in-memory state

whats something else i can do? btw this access token expires

Llukas curious, what is a good way to store an access token? i was thinking using KV bu...

H

Hello, I’m Allie!•1/4/24, 10:06 PM

KV should be fine, unless you need some kind of "Certified" secret store

HHello, I’m Allie!KV should be fine, unless you need some kind of "Certified" secret store

L

lukas•1/4/24, 10:09 PM

Ya thats the only option I feel is available + hashing the access token with a secret

Llukas Ya thats the only option I feel is available + hashing the access token with a s...

H

Hello, I’m Allie!•1/4/24, 10:09 PM

Depending on what Access Token you are trying to secure, that might be overkill too

HHello, I’m Allie!Depending on what Access Token you are trying to secure, that might be overkill ...

L

lukas•1/4/24, 10:10 PM

ebay access_token to an account so i need it secure

K

kian•1/4/24, 10:10 PM

Why isn't KV suitable?

L

lukas•1/4/24, 10:10 PM

well thats what i plan to use but i thought using the value as is might not be safe enough so im thinking of hasing it

K

kian•1/4/24, 10:10 PM

What makes it unsafe when not hashed though?

L

lukas•1/4/24, 10:11 PM

well i guess the question i would ask is, what makes KV secure

K

kian•1/4/24, 10:12 PM

Your Worker would have access to the token either way so if that's the perspective, using Workers has the same security considerations as using KV.

K

kian•1/4/24, 11:09 PM

Should be on the right sidebar when you're in the Workers overview.

K

kian•1/4/24, 11:09 PM

E

Erisa•1/4/24, 11:11 PM

If you have no workers then you'll need to create your first worker before you can access that option

Kkian Workers are just JS and can’t spawn child processes, ffmpeg isn’t going to work

R

Ranjan Mangla•1/5/24, 7:23 AM

thank you very much for your reply, still can we have a worker trigger on file upload in R2, as we have in lambda with s3?

RRanjan Mangla thank you very much for your reply, still can we have a worker trigger on file u...

K

kian•1/5/24, 9:17 AM

Nope

Kkian Nope

R

Ranjan Mangla•1/5/24, 9:41 AM

ok thanks

S

sathoro•1/5/24, 12:27 PM

this is not strictly Workers specific, but I'm wondering if anyone has recommendations for tracking application metrics like timings and counting events? something like Workers Analytics Engine, but a more mature product with nice looking dashboards that is easy to integrate with Workers (a simple REST API is preferred). should be fully hosted, not interested in self-hosting this

Ssathoro this is not strictly Workers specific, but I'm wondering if anyone has recommend...

D

DaniFoldi•1/5/24, 1:02 PM

I recommend Axiom, with the otel-cf-workers package you can add opentelemetry tracing pretty easily - their dashboards are really powerful, and the free tier is very generous

D

DaniFoldi•1/5/24, 1:02 PM

(https://axiom.co)

DDaniFoldi I recommend Axiom, with the otel-cf-workers package you can add opentelemetry tr...

S

sathoro•1/5/24, 1:04 PM

ty! you actually recommended them several months ago for logging but I went with Datadog since they didn't have Logpush integration yet... looks like I might be able to fully migrate to them now

D

DaniFoldi•1/5/24, 1:05 PM

yes, they now have logpush integration that works will all cf datasets, which is cool

0

0xffb3•1/5/24, 3:23 PM

can i run python on workers?

C

Cyb3r-Jak3•1/5/24, 3:24 PM

Not easily. You’d have to compile your python script to WASM to be able to get it to run on workers

K

kian•1/5/24, 4:16 PM

Is this Miniflare 2?

K

kian•1/5/24, 4:16 PM

nodejs_compat modules are a Miniflare 3 thing

K

kian•1/5/24, 4:31 PM

Yeah, Miniflare 3 doesn’t have a Jest environment

P

Pato•1/5/24, 5:12 PM

Hey! anyone knows if i can use pg library in workers?

K

kian•1/5/24, 5:22 PM

With

node_compat = true

node_compat = true

in Wrangler.toml, yes.

P

Pato•1/5/24, 5:26 PM

i have it like that but im still getting this error

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

K

kian•1/5/24, 5:38 PM

I've never seen this output before - what Wrangler version are you using?

P

Pato•1/5/24, 5:39 PM

wrangler 3.4.0

K

kian•1/5/24, 5:41 PM

That looks like you're using a custom build that calls Webpack or similar.

K

kian•1/5/24, 5:41 PM

Wrangler itself uses esbuild.

P

Pato•1/5/24, 5:42 PM

yes im using this :

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

S

subscriptions•1/5/24, 6:27 PM

Hey guys,
If we have a limit on number of invocations per day on the workers paid plan I will move almost all my workload to workers, and few of the developers I have talked to also said the same thing. How to raise a feature request for this? Also, curious why is it not present in paid plan when we have the limits on free plan if anyone could explain a bit further it will really help.

K

kian•1/5/24, 6:29 PM

I'm not sure what you mean by invitations.

K

kian•1/5/24, 6:29 PM

Do you mean requests?

S

subscriptions•1/5/24, 6:31 PM

Sorry updated it, I meant "invocations"

K

kian•1/5/24, 6:32 PM

You can't add a limit if that's what you wanted, you can only add a billing alert so you can go and manually remove the Workers from the routes.

S

subscriptions•1/5/24, 6:33 PM

Yeah, is there a way to request for this feature somewhere?

C

ChaikaOP•1/5/24, 6:33 PM

Also, curious why is it not present in paid plan when we have the limits on free plan if anyone could explain a bit further it will really help

On Paid Plans you just pay for each request over the included amount.
You can't raise the free tier's included requests/day, other then by upgrading to Paid
https://developers.cloudflare.com/workers/platform/pricing/

Pricing · Cloudflare Workers docs

Workers plans and pricing information.

Ssubscriptions Yeah, is there a way to request for this feature somewhere?

C

ChaikaOP•1/5/24, 6:35 PM

There's #workers-feature-suggestions or https://community.cloudflare.com/c/feedback/feature-request/30 on the community forums. I wouldn't hold out hope for it though, virtually no other CF Products have anything like that except Workers Free Tier.

For Standard Billing Model though you can add a CPU Ms Limit per request which can help cap things/make sure a Worker which normally is quick wouldn't take excessively long resulting in a big bill

you sent that ticket from your startup Enterprise account though right? You can already do anything,

Similar Threads

Similar Threads

Similar Threads