feat: ✨ add cross-nodes context propagator to remoting #996
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.
This PR adds first-class support for propagating context values across remoting calls:
Introduced a context_propagator option on remoting config so outbound RemoteAsk/RemoteTell (actors and grains) inject caller context into headers, and inbound handlers extract those values back into the message context.
Added a simple header-based propagator and race-safe echo actor to verify propagation end-to-end in tests (ask/tell for both actors and grains).
Ensured remoting handler test servers use h2c to match the HTTP/2 client and avoid protocol errors.