Repository navigation
Capture worker startup phases before integration cleanup - #157
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.



Refs #123.
The ordinary task-family driver counts primary-client poll starts but loses request timing and handler progress. A fatal worker can remain unnoticed while the driver waits for a result, and a failed stop previously skipped its runner drain.
This test-only change:
The observer/driver component at
1df8875c63a0215432de37ae4ae8eb8af7e847aapasses twelve constructed controls and Ruff. These include additional-client capture, streaming preservation, credential/payload omission, bounded records, cancellation, fatal-worker propagation and cleanup. A two-runner counterfactual fails the initial helper because it skipped its pending peer; the corrected helper drains both. The actualClient.register_worker()contract also caught a registration-route misclassification, which is corrected and now asserted in every real case.Final head
e13e687e1b46c8eaef768483e3b7106ffc3557cb/ treebb669b979b01a9484801a626c8667743480cc698changes only two exception-test setups after Sonar'sS5778review. The observer and integration driver exactly match the installed-qualified component. Sonar39011919697/official app reports0 OPEN/CONFIRMED PR findings; the previous green gate had two actionable findings, which were reviewed and fixed. No rule/profile/threshold change. Exact final-head CI39011919717 passes all10 jobs. Merged at0d33fba37470ebb0a6b292c8e3e3f0e08ec2c61awith the identical reviewed tree and exact parents91c9ee8/e13e687. Independent main CI39012437645 also passes all10 jobs, including HTTP integration. Main Sonar39012437631/App and boundary39012437578 pass. The two new observer files have0 OPEN/CONFIRMED main findings; no zero-backlog claim. Merged remote head is independently404.Published-package check
Normally installed PyPI 2.5.15, source
35aad4ab344cf13e01de3e5f4704380eac1532a6, has all34 package files verified against its immutable source. No editable/path/version substitution. Python3.12 / httpx0.28.1 / fastavro1.13.1, against unchanged published Server2.6.1 / installed Workflow2.5.12, indexsha256:ef043e5c582761e486a64a2ab4226476e17ae4f71682ef59d6b9ddd784d246b6, MySQL8.0.43 and Redis7.The preceding six-case cohort passed business execution but did not distinguish POST registration from control requests. Its observer limitation remains explicit; fresh final-source originals supply the registration result above. No old failure is relabeled.
All local phase containers, networks, data,72MiB dependencies and raw logs were independently absent at06:56:52UTC, before07:15; borrowed images remain protected. Exact candidate and independent main source/HTTP/Sonar checks pass. No package release is needed for these test-only changes.
The original unconstrained stalls remain unexplained. This is improved integration evidence, not an SDK/runtime cause or fix claim. No package source, dependency, version, protocol or publication change.