Skip to content

Keep the clock definition registered across cold redrives - #274

Draft
rmcdaniel wants to merge 2 commits into
mainfrom
agent/sdk-rust/980-redrive-registration
Draft

rmcdaniel wants to merge 2 commits into
mainfrom
agent/sdk-rust/980-redrive-registration

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

The first clock cohort stopped at its first redrive because the cold execution worker had removed the only matching definition registration. The retained NONPASS and exact cleanup are recorded at #272/6870253183. This test-only successor uses a distinct registration-only parent Worker, preserves three cold execution Workers, and adds closed no-registration admission/history controls.

Source evidence at1ed8515: all hosted checks are terminal green; a fresh normal-registry4.17 compile and five ordinary controls passed, with both installed entrypoints ignored. Earlier formatter and no-exec temporary-mount failures remain separate. All source-job container IDs are independently absent.

Security recorded this review step as policy-blocked at #274 (comment). The item is set aside; no further runtime or successor action is selected. Source checks and compiled artifacts are not installed clock, physical-row or release acceptance. Existing #264/#265 holds remain separate and untouched.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Security review of this item is policy-blocked and set aside; no runtime or successor action is authorized by this review step.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel

Copy link
Copy Markdown
Member Author

Exact 1ed8515 compiles as a fresh normal-registry consumer of published4.17 without source overrides. The archive checksum is 6de774879fe8411776b60736391b2c6b426bb1bc125268718004656efd52f5c3; all118 canonical members match the registry source. Manifest/lock remain ecb41e71/750f7f5e, with registry source/archive/index read-only during the offline locked Rust1.86 build.

Test SHA 09f07d271ac9d03a3757edfb8445bd2a554e0b857f7a91f0cfdf0af7a66b445a; build-message SHA 3027d2807bd307b690e2ff23944e2aae77106ee23eef9aeaaf24f3504dd1bb46; compiled parent SHA 70e7783fae37147380d68ad704f8801d5980a2b0e28db6562d2c6c49a1a12863, 22,933,440 bytes. Build exit0/OOMfalse,65s.

The first ordinary-control profile is retained NONPASS: Docker's default no-exec tmpfs refused the synthetic private-copy executable, giving four pass/one failure/two ignored. The corrected private exec-tmpfs profile passes all five ordinary controls, with both installed entrypoints ignored. Both source-control containers and the compiler container are independently absent by recorded full IDs; cleanup passes without OOM. This is source preparation only, not SDK/Server operation or installed clock evidence.

Current exact-head hosted checks are terminal with no pending/failing entries. The first formatting CI remains attributed to2f. Whole-source review, accepted-main verification, a newly pinned build/parent/caller packet and one explicit runtime disposition remain before any new actual cohort. The retained original first-redrive NONPASS is unchanged.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant