docs(hub): Clarify concurrent Hub usage - #1280
Merged
szokeasaurusrex merged 1 commit intoAug 5, 2026
Merged
Conversation
Document that sharing a `Hub` between concurrent threads or tasks is memory-safe but can lead to unexpected behavior. Explain that concurrent `configure_scope` calls are not atomic and may lose updates, and recommend separate hubs. Fixes [#1110](#1110) Fixes [RUST-208](https://linear.app/getsentry/issue/RUST-208/hubconfigure-scope-can-lose-concurrent-updates-on-a-shared-hub)
szokeasaurusrex
marked this pull request as ready for review
August 4, 2026 09:56
szokeasaurusrex
enabled auto-merge (squash)
August 4, 2026 09:56
giortzisg
approved these changes
Aug 5, 2026
szokeasaurusrex
deleted the
szokeasaurusrex/clarify-multithread-hub-limitation
branch
August 5, 2026 10:34
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.
Document that sharing a
Hubbetween concurrent threads or tasks is memory-safe but can lead to unexpected behavior. Explain that concurrentconfigure_scopecalls are not atomic and may lose updates, and recommend separate hubs.This is not a new limitation; it was already documented in
sentry-core's crate-level docs, and these changes just mention the same limitation on theHubandconfigure_scopedocs directly.Fixes #1110
Fixes RUST-208