Hardcode asset worker cohort to 'ent' for latency testing#13855
Conversation
🦋 Changeset detectedLatest commit: f75972a The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
GregBrimble
left a comment
There was a problem hiding this comment.
Personally, I'd probably hard-code both to start with, just so we have the best chance of 100%ing a release with as much of the glue as possible, and then flipping either the cohort loopback back or this back.
But if you want to start with just this, that's up to you :)
|
Codeowners approval required for this PR:
Show detailed file reviewers |
|
You might need a changeset too, to actually trigger a release? I can't remember how this CI is set up. |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
Fixes #wc-4889.
Hardcodes the cohort determination temporarily to help narrow down latency issues.
A picture of a cute animal (not mandatory, but encouraged)
