chore: make SenderInfo available to ApiType#9743
Merged
Merged
Conversation
Persist the `sender_info` field from `struct Ingress` in `CallContext` so it is accessible from `ApiType::Update` (method entry point) and `ApiType::ReplyCallback` (reply callbacks). This allows execution environments to read the sender info throughout the call chain originating from an ingress message. Changes: - Re-export `SenderInfo` from `ic_types::messages` - Add `sender_info()` method to `CanisterCall` - Add `sender_info: Option<SenderInfo>` field to `CallContext` - Persist `sender_info` in protobuf (field 14 on `CallContext`) - Thread `sender_info` through `ApiType::Update` and `ApiType::ReplyCallback` Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
mraszyk
changed the title
mraszyk
changed the title
mraszyk
commented
Apr 8, 2026
maksymar
approved these changes
Apr 8, 2026
alin-at-dfinity
approved these changes
Apr 8, 2026
mraszyk
force-pushed
the
mraszyk/persist-sender-info-in-call-context
branch
from
593dd79 to
d9fe7ec
Compare
daniel-wong-dfinity-org
pushed a commit
that referenced
this pull request
Apr 15, 2026
This PR makes `SenderInfo` available to the relevant variants of `ApiType` (according to the system API availability specified in this [PR](dfinity/portal#6202)). To this end, the PR introduces a new field `sender_info` in `CallContext` to persist the sender info and make it available in callbacks, too. --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.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
3 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.
This PR makes
SenderInfoavailable to the relevant variants ofApiType(according to the system API availability specified in this PR). To this end, the PR introduces a new fieldsender_infoinCallContextto persist the sender info and make it available in callbacks, too.