Don't worry

Is it possible to pass data to firebase database inside cloudflare worker

https://blog.cloudflare.com/exploring-webassembly-ai-services-on-cloudflare-workers/ Is anyone aware of an example repo of model inference from workers as described in this blog post? I'm interested in trying this out.

IIRC, Workers AI, both the GPU integration and the WASM compilation is no longer supported. You might be able to get it running yourself using a custom compiler, but afaik, there aren’t any official examples

It seems from this post it should be possible just with the wasm API. I'll give it a shot and report back.

I mean it technically is, it is just converting your ML model to WASM that’s the issue

This is a route in module worker, in this case, is it possible for the client to trace back my original

flyworker

server? 🤔

You're forwarding all HTTP headers to the client but not the IP or anything

HTTP headers can sometimes reveal information about a server

the

flyworker

server is an expressjs server. 🤔

If you're in control of the server I wouldn't worry, if it's a third party service then I might consider only forwarding the required headers if I was worried about it

can i import python libraries when writing in python and transpiling to js?

will worker buffers the

fetch

respawn? it's an response text stream 🤔

no

I got a timeout error at client but worker log is http 200 🤔

Sure, as long as they don’t call any APIs that are incompatible with Workers

why does

wrangler kv:namespace create NAME

prepend

worker-

to a namespace, while creating a namespace in the workers dashboard does not? 🤔

⛅️ wrangler 2.15.1 
--------------------
▲ [WARNING] No configured name present, using `worker` as a prefix for the title
🌀 Creating namespace with title "worker-NAME"
✨ Success!

if youre in a directory with a wrangler.toml, it prepends the name of the worker (probably so you can find the namespace easier)

ah, okay – this is for a pages functions project , so there's no worker or wrangler.toml.

Ah yeah - thats good feedback then, it does seem a bit strange

most likely the functionality predates the existence of pages projects

I would probably report it on so someone can triage and see whether it needs adjusting

okay, will try to do that if i have time. there are a bunch of typos and mistakes in the wrangler -> commands documentation, so hopefully someone is going to proofread and correct them soon. e.g. under

kv:key put

the action refers to

delete

https://developers.cloudflare.com/workers/wrangler/commands/#put

--binding 
  The binding name of the namespace, as stored in the wrangler.toml file, to DELETE.
--namespace-id 
  The ID of the namespace to DELETE.

thanks for the clarification – correctly named namespace is good to go now 🙂

Is anyone else here using Wasabi with a Cloudflare Worker? I noticed sometimes I'm getting a 403 with

Account Connection Limited

as the response text.

does anyone here use cf-workers-status-page?

🙌

Heya! 😂

I think something is off with how cloudflare monitors kv writes - nothing has changed on the repo or in your usage (it’s the only thing there)