fix(cloudflare): Send correct events in local development#19900
Open
fix(cloudflare): Send correct events in local development#19900
Conversation
Contributor
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Deps
Bug Fixes 🐛Cloudflare
Other
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
Contributor
size-limit report 📦
|
JPeer264
force-pushed
the
jp/fix-local-cloudflare
branch
from
09affa3 to
f990653
Compare
Lms24
approved these changes
Mar 20, 2026
Member
Lms24
left a comment
Lms24
left a comment
There was a problem hiding this comment.
Looks reasonable to me! So to confirm: The behavior when deploying to cloudflare was unaffacted? I think the change makes sense either way. Was just curious based on our convo yesterday.
| await flush(timeout); | ||
| } | ||
|
|
||
| client?.dispose(); |
Member
There was a problem hiding this comment.
super-l: We could get of the optional chaining by moving the dispose call into the if block above. Feel free to disregard though
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using
wrangler devthere is an isolation scope spawned as in production, but there is only one for the worker and the durable object (DO) (while in production these two get 1 each). With local development this could be a problem with the flush. The RPC is done inside the worker, which means at the time the DO is getting called the initial worker async local storage (ALS) is overwritten by the DO. That leads to a wrong client when the worker flushes after all calls are done. Here a little mermaid graph to showcase this a little better:sequenceDiagram participant W as Worker participant ALS as AsyncLocalStorage participant DO as Durable Object participant S as Sentry Proxy W->>ALS: Initialize ALS context (Worker client) W->>DO: stub.fetch(request) DO->>ALS: Initialize ALS context (DO client) Note over ALS: ALS now holds DO client<br/>(single-threaded wrangler dev<br/>overwrites Worker context) DO->>S: flush() ✅ (DO client correct) DO-->>W: Response W->>ALS: getIsolationScope().getClient() Note over W,ALS: ❌ Returns DO client instead<br/>of Worker client W->>S: flush() ❌ (wrong client) Note over W: Worker events not flushed<br/>or flushed to wrong clientAs we already have the
clientavailable inside the flush function (as we pass it through), we can directly call it if it is available.Closes #19901 (added automatically)