Repository navigation
docs: explain Rust stable activity identity in all eight locales - #397
Merged
Merged
Conversation
|
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
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.
Rust activity handlers need a stable logical activity ID for downstream deduplication and the owning workflow instance/run for correlation. All eight Rust guides now document the published4.9
ActivityContextaccessors, with an identical handler deriving a namespaced key and refusing missing identity before effects. All eight execution-guarantees guides link that service-mode recipe. Refs #396, sdk-rust#139 and .github#211.The guide distinguishes logical activity identity across retries from task/attempt identity, immutable received optional values, older claims, inline locals, Server-free tests and worker sessions. Installed
Cargo.lockmust actually select4.9 or newer; the site's independently selected tuple is unchanged. Downstream idempotency still needs an API or durable effect ledger that honors the key. The example does not perform a payment or provide resumable checkpoints; shared .github#218 remains separate, and the delivered guide will be linked from closed Website#272.Normal installed4.9 acceptance, OIDC39967443675 and API39967624766 pass. Source/tag
93d3c3aa78be4347045f50833ffcdc02dcabc4ed; normal registry/archive/lock checksumbe21bb5b033cc8db364f1f9e3d789607eb6eff976126965cfc95072146c220a6. Website independently checked all70 Rust-source/README files against immutable source and the live API version/anchors. The SDK owner compiled and ran this exact helper in the normal installed Rust1.86 graph:5bc0013b04c501791ebee8d5768fe5d7ac744c853ff58cc2c6b6ca4a807e16c0.Local checks: seven reviewed-source hashes current, every executable block matches English, translation inventory and whitespace checks pass. Exact-head all-locale CI, Sonar review, actual Pages publication and all eight live guide pairs precede delivery. No new local dependency/compiler/runtime or source overlay. SDK/shared product closure remains with their owners.
Delivery complete: normal merge bd33ba3; exactCI39973236140/allchecks/Sonar0, artifact39977452931 and actualPages39978971911 pass. All16 live routes/bidirectional localized links/fullmetadata/accessor rows/actual copiedhelper/48 exact-source paragraphs and12 en-ja-zh390px lightdark views verified. Website396 complete; SDK139/shared211 closure stays with owners, shared218 checkpoint requirement remains separate.