Repository navigation
Document Python worker sessions and rebuilding local state - #377
Merged
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
October 23, 2026 09:27
|
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.
Python users cannot find a worker-session example. All eight locales now show typed session options, sequential remote activities, worker capabilities, disposable local state and holder-loss recovery in the Python service guide. The embedded session guide links to that recipe and summarizes the boundaries.
Refs #349. Published-package qualification uses normal Python SDK2.9.0 and published Server2.11.0 with its published scheduler role. Three originals complete within unchanged45-second deadlines: same-holder cache reuse, actual killed-holder/rebuilt-state recovery, and explicit close producing a handled activity timeout. Normal and holder-loss controls have zero repairs; explicit-close has two normal scheduled repair passes. Exact definitions, probe and read-only audit are included in the receipt.
The first API-only closed-session original failed its40-second observation limit because the fixture omitted required maintenance. Its database/identity remain separately frozen; the successful fresh complete-role controls do not relabel that failure. The guide names the required scheduler and does not promise immediate session-closed exceptions, durable local state or automatic reopening of terminal sessions.
Validation: all seven reviewed-source hashes and executable code parity pass locally. Exact-head qualification builds all eight locales. Publication and16 live-route/actual-link checks follow normal merge.