Thanks @kian - I'll give that a go. Any way to grab the history of all active Workers at once?

dont provide the worker name in the query filter and set the worker name as a dimension

Something like this:

gql
query {
  viewer {
    accounts(filter: {
      accountTag: "<put ur account id here>"
    }) {
      workersInvocationsAdaptive(
        filter: {
          date_geq: "2023-03-01",
          date_leq: "2023-03-31"
        },
        limit: 10000,
        orderBy: [sum_requests_DESC]
      ) {
        dimensions {
          scriptName
        }
        sum {
          requests
          wallTime
        }
      }

    }
  }
}

If you have any unbound workers the wallTime is microseconds iirc. Multiplying by

0.000000125

should get you the GB-sec value

Thanks!

Hi everyone, does anyone know where is

unsafe

documented? As in

[unsafe.metadata.placement]
mode = "smart"

from https://developers.cloudflare.com/workers/platform/smart-placement/#enable-smart-placement-beta Because I'm getting this error and I can't make any sense of it.

▲ [WARNING] Processing wrangler.toml configuration:

    - "unsafe" fields are experimental and may change or break at any time.
    - "env.dev" environment configuration
      - "unsafe" exists at the top level, but not on "env.dev".
        This is not what you probably want, since "unsafe" is not inherited by environments.
        Please add "unsafe" to "env.dev".



✘ [ERROR] Processing wrangler.toml configuration:
If you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new/choose

    - The field "unsafe" is missing the required "bindings" property.

looks like you're trying to use smart placement in the dev env, is that right?

If so, you'll want the heading to be

[env.dev.unsafe.metadata.placement]

(toml sucks)

That error looks like an old version of Wrangler

> The field "unsafe" is missing the required "bindings" property.

That validation was removed in 2.12.0 - hence this

I'm not sure, I'm pretty new to this. I'm using the exact same code from the documentation

[unsafe.metadata.placement]
mode = "smart"

there's a

[dev]

section above and some other things below. Does that count as "in the dev env"?

So I guess updating wrangler is the first step to fix this

is using @cloudflare/workers-types the preferred way to support TS in workers?

Yup

Where is WebSocketPair imported from? All ws examples error on TS: Cannot find name 'WebSocketPair'

ah, do we have to hack our types.d.ts file? https://github.com/cloudflare/workers-types/issues/84

seems to work but I hate monkeypatching. Will TS be get first-class support in workers?

It’s just in workers-types already

That’s a pretty old issue

It is: https://gist.github.com/helloimalastair/126e8c64963aeafc27c7c1136583dda3#file-cf-d-ts-L1819

yeah - this is the only way I can get TS to not error, have to monkeypatch. By default any ts file will complain that youre trying to instantiate WebSocketPair which is a type

VSCode doesn't appear to throw any errors:

In a TS file

What version are you running?

of ts? or wrangler? or cf types?

CF Types

So I see that you can modify the response headers if you await the origin response and then return it. However, is that a good idea to do when the response could be a multi-GB file?

"@cloudflare/workers-types": "^4.20230404.0",