Fix schedule probe worker capability refusals - #281
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
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 schedule runner's synthetic Python workers copied the SDK Worker affinity manifest even though they only poll and complete tasks. That advertised local activities and worker sessions without the corresponding routing capabilities, so published Server 2.4.28 rejected registration with
worker_capability_manifest_mismatch.Both Python probes now declare explicit affinity refusals using the published SDK's protocol versions. This matches what the probes implement and allows schedule lifecycle and cross-language dispatch qualification to reach their actual scenarios.
JavaScript syntax and whitespace checks passed, and all PR checks are green. Published conformance passed all 15 scenarios after rerunning the affected Python lifecycle and both PHP/Python dispatch directions, retaining the ten unchanged results from the same immutable tuple. Both schedule dispatch directions reached their intended worker and completed.
Tuple: Server 2.4.28 at
sha256:4d177da9852477fc774cc68e84aa8e2f787d756370437f9519ae415f7c388825, bundled Workflow 2.2.19, CLI 2.0.0, PHP SDK 2.1.6, Python SDK 2.3.7 and Waterline 2.0.7. The focused run used runneredd23764from 2026-09-29 19:54:54 to 19:58:47 UTC. Each artifact's actual installation was verified, including a fresh Waterline Composer install.Related release: #280.