anyone else experiencing an outage with some workers?
anyone else experiencing an outage with some workers?
Wcan you expand?
Wwhat issue are you seeing?
Awe were seeing 500 errors but we think they may have been transient. will follow up shortly, thanks
Aupdate: subsequent retry did not have the 500s
Dhas anyone actually managed to use the API to bind a D1 database to a worker? I have tried every configuration known to man and I cannot. I get this everytime: [ { code: 10202, message: 'workers.api.error.invalid_script_config' } ] I get random success messages, but bindings do not get updated.
Das far as i can see - despite the API endpoint, it's impossible to use /settings. every time i get a success 200 OK message from the API and nothing gets updated. I noticed the dashboard uses /versions but you have to pass the whole codebase to the API endpoint which I really wanted to avoid doing.
SHi team, I'm attempting to use a library which imports cockatiel. I don't have any code execution occurring but simply importing it causes
I'm not sure how to best go about fixing this as it is purely from within an import statement for a library that I didn't write.
Uncaught Error: Disallowed operation called within global scope.. I believe it is related to this block of code when looking at the wrangler server compilation... in particular the var neverAbortedSignal...I'm not sure how to best go about fixing this as it is purely from within an import statement for a library that I didn't write.
Bis there an example of how to integrate a worker particularly a workflow into an existing pages app that uses a framework, e.g. astro? there are so many questions compared to the docs example where a template is used
O@Walshy It looks like a cron job failed to run today on one of my workers - I got no notification about it or anything
ODeployment id e322077b-e8bf-4142-9e90-db3d07cecb7c
Iare you referring to http/rpc service bindings between workers?
BNo. Workflows with astro framework
MI got this error, anywhere I can find the filesize limits?
{
"stack": "AiError: 3006: Request is too large\n at Ai._parseError (cloudflare-internal:ai-api:76:20)\n at async Ai.run (cloudflare-internal:ai-api:57:23)\n at async Object.fetch (index.js:22:24)",
"name": "Error",
"message": "3006: Request is too large",
"timestamp": 1730282388860
}
{
"stack": "AiError: 3006: Request is too large\n at Ai._parseError (cloudflare-internal:ai-api:76:20)\n at async Ai.run (cloudflare-internal:ai-api:57:23)\n at async Object.fetch (index.js:22:24)",
"name": "Error",
"message": "3006: Request is too large",
"timestamp": 1730282388860
}
FSadly this limit is not mentioned here -> https://developers.cloudflare.com/workers-ai/platform/limits/
FI doubt the 100MB (and greater) request size limit applies to AI workers- -> https://developers.cloudflare.com/workers/platform/limits/#request-limits
MThe image is like 3,5mb so
MAnd yeah there's no limit so 
FIf the raw image size is 3,5mb this might blow up ~30% with base64 encoding, some AI APIs I know have a 4MB hard limit for image size (in base64).
FDunno if this applies to Cloudflare AI though.
MHmmm, is there a way to easily compress the image in a worker?
FMYeah, not really what's needed here I think. I want to use AI to classify some images but might not work if there's such a small limit
FYou can of course do this manually inside the worker, but you have to code this yourself (you'll kind of pay for the conversion in both ways, either via the image service or via CPU milliseconds for your worker).
MThanks for the help anyway
F
FPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.MAnyone from cloudflare who could officially answer this?
CI’d recommend asking in #workers-ai
MGood one
0is the pulumi/terraform provider don't support workers static assets yet is it?
FGit heavily relies on a working filesystem (as git effectively uses the filesystem as its database), I don't know if a VFS shim around R2/S3 will ever make git happy. It may be easier to write/modify a git implementation to use R2/S3 operations directly and skip the VFS layer (like Microsoft did with ditching VFSForGit and moving everything in their git fork)
DQuick maybe dumb question. Can you define a worker entry point in a worker and access and call the class and it’s methods in the same worker? I understand with RPC you can export the class in the same file as the module default export and it can be used in other workers. But wondering if it can be used in the source worker and other workers
II think you can bind it directly within that same worker and access it via
env , here’s a demo: https://github.com/cloudflare/js-rpc-and-entrypoints-demo/tree/main/public-admin-api-interfaces/db-service. I haven’t tried it myself thoughDThanks I’ll try that out
DI’m also gonna try calling a rpc in a workflow. Wondering if that will work
GHello everyone, have any of you tried to deploy nextjs on workers?
GThanks ! Which is better cloudflare pages or workers for nextjs
FNo clue. Workers are more up-to-date and powerful though.
DWorking through this example... Is this bug described here still outstanding? https://github.com/cloudflare/js-rpc-and-entrypoints-demo/blob/12f7f2e10a4543c229554bcec4cba139e16594ce/public-admin-api-interfaces/db-service/wrangler.init.toml
GitHub
Contribute to cloudflare/js-rpc-and-entrypoints-demo development by creating an account on GitHub.
Ais there a way to have a subrequest outlive the parent request in a worker?
Ae.g. POST /foo -> worker kicks off an internal fetch() to /someapi, meanwhile responds to the POST /foo with (202)
Ain my testing the subrequest is getting killed when the 202 response is sent
Cctx.waitUntil
CCloudflare Docs
The Context API in Cloudflare Workers, including waitUntil and passThroughOnException.
Cyou only get 30s of real time though for it to finish, or it'll get cancelled anyway
Agot it!
Athat works like a charm, thanks very much
AHey 
I am trying to call a DO from Worker B when DO is exported from worker A.
Worker A looks like this:
And the index.ts in worker B is a fetch calling a DO stub (with RPC), and exporting the fetch.
On Worker A, it's a simple fetch + DO sqlite, both exported.
Worker A deploys fine and works fine with DO. I get this error on deploy for worker B (that should use the DO from worker A):
Any idea what I could be doing wrong?
I am trying to call a DO from Worker B when DO is exported from worker A.
Worker A looks like this:
And the index.ts in worker B is a fetch calling a DO stub (with RPC), and exporting the fetch.
On Worker A, it's a simple fetch + DO sqlite, both exported.
Worker A deploys fine and works fine with DO. I get this error on deploy for worker B (that should use the DO from worker A):
Cannot create binding for class in script 'worker-A' that does not exist [code: 10061]Any idea what I could be doing wrong?