Conversation
`jurisdiction()` returned the raw binding, so stubs from a jurisdiction-restricted namespace got no fetch span and never propagated RPC trace context. It now returns a namespace instrumented the same way as its parent. Fixes getsentry#24442 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
msnelling
requested review from
isaacs and
mydea
and removed request for
a team
September 16, 2026 17:46
JPeer264
requested review from
JPeer264
and removed request for
isaacs and
mydea
September 17, 2026 06:55
JPeer264
approved these changes
Sep 17, 2026
JPeer264
left a comment
JPeer264
left a comment
Member
There was a problem hiding this comment.
Amazing. Thanks a lot for adding it.
This has unit coverage only: local workerd throws "Jurisdiction restrictions are not implemented in workerd", so an integration suite can't exercise it.
This is ok, we'll add some deployed worker tests soon and I'll add this case then there too (#24280)
JPeer264
approved these changes
Sep 17, 2026
msonnb
pushed a commit
that referenced
this pull request
Sep 17, 2026
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #24450 Co-authored-by: JPeer264 <10677263+JPeer264@users.noreply.github.com>
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.
instrumentDurableObjectNamespacespecial-casesgetandgetByName, and binds every other function to the raw target.jurisdiction()therefore returned an uninstrumented namespace, so stubs from a jurisdiction-restricted namespace got no fetch span and never appended__sentry_rpc_meta__. Apps using data-location jurisdictions (for example EU residency) lost trace continuity at every Durable Object call.jurisdiction()now returns a namespace instrumented the same way as its parent, with the samepropagateRpcTracesetting.This has unit coverage only: local workerd throws "Jurisdiction restrictions are not implemented in workerd", so an integration suite can't exercise it.
Split out of #24447, which now covers #24443 only.
Fixes #24442
yarn lint) & (yarn test).Written with AI assistance (Claude Code).