fix(I199-followup): use anonymous() in 2 example test sites #3

Merged
buildagent merged 1 commit from fix/i199-sdk-examples-anonymous-ctor into main 2026-05-27 23:12:03 +02:00
Member

Summary

SDK CI's clippy + check on examples fails after the I198/I199 lockstep merges:

error[E0599]: no function or associated item named `new` found for struct `ixt_sdk::types::InvocationContext`
  --> sdk/ixt-sdk-rust/examples/async_init_demo.rs:627:37
  --> sdk/ixt-sdk-rust/examples/lifecycle_demo.rs:648:37

Two stale InvocationContext::new("test-sender".to_string()) calls in the embedded test modules of the example binaries. Both files already use InvocationContext::anonymous(...) correctly elsewhere (lines 484/498). Migrate the 2 remaining sites to match.

Pre-1.0 SDK mirror has no new() constructor — anonymous(source_module: impl Into<String>) is the canonical opaque-actor ctor (matches the runtime's spec 21 InvocationContext shape).

Why it slipped through

PR #2's local validation ran cargo test -p ixt-sdk --lib which doesn't compile examples. SDK CI's --all-targets does, catching it post-merge.

Validation

  • cargo check --examples — clean
  • cargo test --examples --no-run — clean
  • cargo clippy --all-targets -- -D warnings — clean

Follow-up

After merge, the parent h-dv/ixt superproject pin bump will land separately.

🤖 Generated with Claude Code

## Summary SDK CI's clippy + check on examples fails after the I198/I199 lockstep merges: ``` error[E0599]: no function or associated item named `new` found for struct `ixt_sdk::types::InvocationContext` --> sdk/ixt-sdk-rust/examples/async_init_demo.rs:627:37 --> sdk/ixt-sdk-rust/examples/lifecycle_demo.rs:648:37 ``` Two stale `InvocationContext::new("test-sender".to_string())` calls in the embedded test modules of the example binaries. Both files already use `InvocationContext::anonymous(...)` correctly elsewhere (lines 484/498). Migrate the 2 remaining sites to match. Pre-1.0 SDK mirror has no `new()` constructor — `anonymous(source_module: impl Into<String>)` is the canonical opaque-actor ctor (matches the runtime's spec 21 InvocationContext shape). ## Why it slipped through PR #2's local validation ran `cargo test -p ixt-sdk --lib` which doesn't compile examples. SDK CI's `--all-targets` does, catching it post-merge. ## Validation - `cargo check --examples` — clean - `cargo test --examples --no-run` — clean - `cargo clippy --all-targets -- -D warnings` — clean ## Follow-up After merge, the parent `h-dv/ixt` superproject pin bump will land separately. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
SDK CI's clippy + check on examples fails after I198/I199 lockstep merge:

  error[E0599]: no function or associated item named `new` found for
    struct `ixt_sdk::types::InvocationContext`

Two stale `InvocationContext::new("test-sender".to_string())` calls in
the embedded test modules of the example binaries:
- examples/async_init_demo.rs:627
- examples/lifecycle_demo.rs:648

Both files already use `InvocationContext::anonymous(...)` correctly
elsewhere (lines 484/498). Migrate the 2 remaining sites; ship-1.0 SDK
mirror has no `new()` constructor — `anonymous(source_module: impl Into<String>)`
is the canonical opaque-actor ctor (matches the runtime's
spec 21 InvocationContext shape).

The miss slipped through PR #2 because `cargo test -p ixt-sdk --lib`
doesn't compile examples. SDK CI's `--all-targets` does.

Verified locally:
  cargo check --examples — clean
  cargo test --examples --no-run — clean
  cargo clippy --all-targets -- -D warnings — clean

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
h-dv/ixt-sdk-rust!3
No description provided.