This repository was archived by the owner on Aug 14, 2024. It is now read-only.
docs: Clarify Concurrent Hub usage#741
Open
docs: Clarify Concurrent Hub usage#741
Conversation
Explains the different concurrency models and how `Hub` propagation should happen for these.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Explains the different concurrency models and how
Hubpropagation should happen for these.These use-cases are mostly inspired by similar documentation I recently added for Rust here: getsentry/sentry-rust#509
The current set of APIs though are cumbersome to use for this manual copy / binding. It might be worth brainstorming or RFC-ing better more streamlined alternatives for this.