Repository navigation
Prepare Python SDK 2.6.2 entry and activity worker safety fixes - #174
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.
Purpose
Prepare Python SDK 2.6.2 with the qualified entry-binding safety fix from #170 and default synchronous activity worker fix from #172.
Scope
Only the three machine-owned version fields in
pyproject.tomladvance from 2.6.1 to 2.6.2. Runtime, dependencies, supported Server declaration and worker protocol remain exact mergedcecdf4aa6d164f7a9041a6c01d2bbc22f9017195/ tree80e55045077cc93d1fcf93bf9a789ae2de30eca6.Both source PRs and their independent main qualifications pass. #171 records five unchanged-source/published counterfactual failures, final focused and official corpus passes, plus genuine normal-client HTTP evidence on published Server 2.9.7: the default published worker stalls the event loop; the correction runs blocking handlers on bounded physical threads while workflow progress and actual heartbeats continue. Original fixture/corpus failures are preserved and no assertion or policy is weakened. .github#221 records the separate pre-entry refusal and recovery controls.
This metadata tree needs fresh normal candidate/main qualification before immutable publication. Exact PyPI identity, normally installed fixed-package compatibility/HTTP acceptance and downstream consumers remain pending. No Server/native/frozen adoption is included.