check out the Examples page I think I saw this scenario there last week

You can see how https://github.com/cloudflare/wrangler-action handles secrets in GH Actions, as an example

@HardAtWork , do you know what the command is? Not familiar with GitHub actions as I am using azure pipelines. Cheers. Was thinking of

echo $(MY_SECRET) | wrangler secret put MY_SECRET

but this will show the secret in console.

anyone know a Workers-compatible library for converting PNGs to JPG? been doing some research and can't find one so far

Looks like that’s what the action does: https://github.com/cloudflare/wrangler-action/blob/4c10c1822abba527d820b29e6333e7f5dac2cabd/entrypoint.sh#L126

If you pipe the echo, then it shouldn’t log it

I just realized I might be able to use Browser Rendering to use

canvas

to convert PNG to JPG... I wonder if that will be really slow though

that would be a bit overkill but would certainly work

I've done stupider things

Probably a lot less painful than having to compress some Rust crate to fit

yeah and depending on how efficient Browser Rendering is it could be really fast

do we have examples for a workers that receive an input fileuplaod as parameter?

Hi, following up on this https://discord.com/channels/595317990191398933/779390076219686943/1108800514507939971

Regarding cloudflare workers usage limit

@sathoro Do you do traffic shifting when deploying new versions of your Workers in production?

🤣

I am taking moving fast and breaking things to a different level

Are you still getting those emails? There was an issue, starting around the 17th, lasting until around the 19th, resulting in CRON triggers triggering more then once. It looks like that Status Page uses Cron triggers, probably related: https://www.cloudflarestatus.com/incidents/pg9ms2p91nsf (CRON Triggers were doubling, and at least for one of mine, even triple executing. Would drive up KV Usage 2x-3x what you were using before)

Not getting the issue any more, thanks

every few weeks I asked the exact same question hoping somebody will have an amazing solution that isn't hard to implement lol.

anyone have a workaround for wrangler dropping support for https?

▲ [WARNING] Miniflare 3 does not support HTTPS servers yet, starting an HTTP server instead...

i use a cloudflared tunnel but that wouldn't help with offline development

Anyone else having connectivity issues with logs and such?

I am having an issue with a specific worker(others are fine), any action done to it except quick edit in dash fails with 10013 (wrangler and dash). everything worked yesterday and no changes have been done since. anyone have a clue?

Issue appeared to be DNS records and worker config became desynced. redeploying with one new custom domain then next deploy removing all of them solved it.

I'm getting

bash
service core:user:chainfuseapi-plugins-rss2json: Uncaught Error: Dynamic require of "node:stream" is not supported
  at index.js:1:383
  at index.js:18:4350
  at index.js:1:500
  at index.js:245:2751
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

But it says it's supported here: https://developers.cloudflare.com/workers/runtime-apis/nodejs/streams/ Running

wrangler

3.0.1 and

compatibility_flags = [ "nodejs_compat" ]

in the

wrangler.toml

I'm having trouble with proxying websockets through workers. Workers will throw an error like this:

worker.js:233 Error: No response!
    at __facade_sw_fetch__ (worker.js:176:15)
    at __facade_invokeChain__ (worker.js:25:12)
    at Object.next (worker.js:22:16)
    at jsonError (worker.js:231:34)
    at __facade_invokeChain__ (worker.js:25:12)
    at Object.next (worker.js:22:16)
    at scheduled (worker.js:213:26)
    at __facade_invokeChain__ (worker.js:25:12)
    at __facade_invoke__ (worker.js:28:12)
    at worker.js:181:43

Any ideas? https://discord.com/channels/595317990191398933/1110432425437298729

I am creating two database records in my request handler, one immediately and then I do an api call to external and after the response has been returned, I create a second entry. Those have the same "createdAt" timestamp though, even I know that this can't be the case. I need them to have different stamps because I need to see which one was created first later. Is there a better hack than simply adding like 100ms onto the second date?

are you getting createdAt from Date.now() or is this all through an ORM/default field added by the DB?

not from db, it's provided by my code