Thank you for everyone who helped with this. We really appreciate and are thankful for the prompt resolution from everyone involved.

opentelemetry in worker?

I have also had these same questions, I haven't managed to find much/any clear documentation on how the isolates work in regards to quotas and such

Isolates in general or specifically for Service Bindings?

Each request has it's own CPU limit, and the isolate has a memory limit - concurrent requests will be sharing the same memory, so using 80MB might be okay for a single request but as soon as there's two at the same time, expect exceptions. If you're using all Unbound in your Service Binding chain, you get a flattened duration since Worker A's CPU isn't idle as it's working on Worker B's response. If you're using Bundled anywhere then it's a new request and it gets 50ms of CPU time. Memory limits have some grace, as there's a soft eviction if you go slightly over and a hard eviction if you go way over - you can read up on it at https://www.infoq.com/presentations/cloudflare-v8/ which is also a pretty cool resource for the implementation details of Workers in general.

You can also read into a bit of

workerd

if you feel like it - i.e

It'll only go so far though - the limit enforcer isn't OSS

Hello everyone, I am currently building a website with sveltekit and had some builds on cloudflare pages fail because I imported a file called logo.png while the source file was called logo.PNG (with the extension in uppercase). Building locally and running dev worked but when I deployed to pages vite build failed with: > [vite:asset] Could not load /path/to/logo.png Not quite sure if this is intended so I thought I should bring it up here. Changing the file extension to lowercase fixed the issue.

Are you perhaps developing on a system that allows case-insensitive filenames (windows, mac)?

yup

Linux generally uses a case-sensitive filesystem, which is what Pages uses to build

I would recommend you make the dir/filesystem you're developing in case-sensitive - all modern OS versions have ways to do this

I'm mainly using the serverless function to pull static data for a data visualization web app.

Yup 😆

is there some sort of a restriction on what error codes the worker can return? When I return 403 response code the logs say that it returns 403, but the actual response is never returned to the browser, when I return 204 it works just fine.

You should be able to return 403 no problem, are you seeing anything in the worker logs or?

POST /api/document/upload 401 Unauthorized (5.87ms)

or

POST /api/document/upload 403 Forbidden (9.48ms)

I try to upload a file and when a user is not authenticated or does not have sufficient rights I return respective codes

when I try to download the file 401 works fine

so I'm kind of puzzled

is it FormData that somehow affects the worker?

hmmm, it seems that doing

const formData = await context.request.formData();

before any checking logic for 401 and 403 (or returning any response at all) solves this issue. Any idea why?

Hi. I'm new workers and am trying to understand how I control access to workers and durable objects. Right now it seems that once I've published a worker, anyone in the world can call it. How can I limit this so that my workers & durable objects can only be called from same origin or from pages functions. Are there any articles I can read on this?

What are these trace and test things in the type definitions for ExportedHandler?

Trace Workers: https://blog.cloudflare.com/workers-for-platforms/#trace-workers And Test Workers (mainly for internal workerd use right now): https://github.com/cloudflare/workerd/pull/341

email is missing from that interface

Maybe its the version? I'm on 4.20230215.0 of @cloudflare/workers-types

Has anyone hit the following error using `jest-environment-miniflare`:

SyntaxError: Unexpected token ':'

      at VMScriptRunner.runAsModule (../node_modules/jest-environment-miniflare/node_modules/@miniflare/runner-vm/src/index.ts:34:20)

I'm running

jest

with

NODE_OPTIONS=--experimental-vm-modules

It's a Typescript file

It looks like jest might not be transpilling your code. See the example here and ensure you have ts-jest or babel setup https://github.com/cloudflare/miniflare-typescript-esbuild-jest/blob/3c8ae62e04f3313a30aa85f6f96feb4c8233f1ac/jest.config.js#L2