Repository navigation
Explain Python heartbeat refusal and callback exit boundaries - #376
Merged
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
October 23, 2026 09:23
|
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
2 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.
The Python heartbeat guide omits the refusal and callback-exit behavior delivered in SDK #186. All eight locales now explain
can_continue=false, original Server reasons, the cancellation distinction, cooperative exit and physical-slot retention. The timeouts page links to the language-specific explanation; existing helper-thread recipes remain linked.Refs #375 and published Python2.9.0 acceptance. Normal installed source was inspected directly. The upstream46 synthetic heartbeat/lease controls establish SDK handling, not live Server timeout admission or Workflow#878 acceptance. The text explicitly identifies2.9.0 and does not infer support from the older separate installation tuple.
Validation: all seven locale source hashes and executable code parity pass locally. Exact-head qualification builds all eight locales. After normal merge and Pages publication, verify all16 Python/timeouts routes and the actual localized links before returning the receipt to the SDK owner.