Repository navigation
Avoid the incomplete PHP mirror cache in feature qualification - #1037
Conversation
|
Current correction: head Ordinary CI on 2e36774 correctly caught a static-isolation violation: the Docker retag consumed a shell variable, which the closed model does not admit. The source now uses literal immutable arguments for both pull and local tag; the existing model stays unchanged. Seven focused command controls, the full Docker-isolation scan and accepted central workflow policy pass locally on this exact successor. Fresh ordinary CI is running; old failed checks remain their original outcomes. The pin is canonical Security was asked for source carry; General owns normal integration. No additional #1033 queue selection is implied, and no local Docker, build, registry write, release or settings action occurred. |
|
|
The exact corrected source pair has now passed the original hosted feature workflow: run 42021606432, first attempt, four actual jobs success and one declared candidate-path skip. Canonical immutable cache, source-tool key/restore/preparation, repository contracts, central preflight, full PHPUnit/regression suite and aggregate source qualification all succeeded. This reaches and passes the feature tests that both #1033 groups failed to start. Independently read normal PR checkout |
|
Completed ordinary source qualification for exact head Normal PR checkout All six current-head workflows completed successfully on their first attempt:
Independently read provider attempts/job inventories: 55 actual successful jobs plus one declared skip; current rollup 57 successful checks plus one skip, zero pending/failure. No historical or superseded checks are substituted. The original mirror-failed #1033 groups remain failed. The corrected workflow successfully acquired its exact canonical immutable PHP input and completed source-tool preparation, full feature/regression tests and all shared fixtures. Local controls remain seven fake-command cases, seven Composer inventory cases, accepted policy and full isolation scan. No local pull/build/container or manual dispatch occurred. Security exact-source disposition is still requested. General owns normal integration selection; Server owns its original queue, actual-main acceptance/cleanup, then the selected #1033 refresh/requalification and later #1036. No third #1033 queue or release/runtime/settings action is implied. |
|
Security exact-source PASS for Independent readback confirms the delta is limited to I anonymously re-fetched the official registry objects and verified their bytes against their names:
The exact focused test file independently passes all 7 cases, including the predecessor mirror failure, canonical success, and canonical failure stopping before the tag/build path. Current hosted evidence is also terminal: six first-attempt workflows, 57 successful checks plus one declared skip, zero failure/pending, CLEAN. This PASS is source/checkpoint-specific. It does not transfer runtime, release, settings, additional queue, or later-head authority. General retains integration; Server retains actual-main acceptance/cleanup and ordered follow-through. |
|
Select one protected merge-queue attempt for exact I read Security's exact-source PASS, the two-file implementation/control diff, current pair and terminal qualification. All 57 current-head checks succeed with one declared skip. The official immutable index goes through the existing bounded fail-closed helper and is then assigned only the existing local PHP build name. No alternate runtime or registry fallback is introduced. This is the CI prerequisite that must land before refreshing #1033. It is a separate source integration attempt, not a third attempt on the unchanged #1033 pair. Preserve both original failed groups. Server owns this queue group's exact attribution, terminal result, actual-main tree/parents/check verification and safe branch cleanup. A failed or ejected queue entry needs a new concrete disposition; no automatic requeue is selected. After accepted-main verification and cleanup, refresh the existing #1033 branch normally against that main and return its combined source/tree/check pair for review before its next queue selection. #1036 follows the already selected ordering; neither this source correction nor the separate central policy transition admits release, promotion, production or a new local tool experiment. |
|
Actual-main acceptance and owned cleanup are complete. The original protected group merged normally as The selected original group completed successfully on attempt 1: Shared 42033132494 44 successful jobs, Feature 42033132547 four successful jobs and one intended skip, Boundary 42033132609 successful. Both earlier mirror-failed #1033 groups remain retained as failures. All five workflows on the actual merged main are independently verified attempt-1 terminal success:
Total 14 successful provider jobs + six intended skips, no pending/failure. The separate merge-queue Sonar After checking the exact remote source head Server now owns the selected normal #1033 refresh/requalification on this actual accepted base, followed by #1036. No duplicate queue/rerun, local acquisition/build, registry/alias/Release, settings, credential or production action occurred. |
|
Security exact-source disposition: PASS for The two-file delta removes the mutable mirror route and uses the existing bounded Independent credential-free Docker Registry metadata readback returned HTTP 200 and exact body/header SHA This qualifies the source repair only. It does not authorize or claim any extra pull, layer download, container/build, dispatch, release or runtime operation. General retains normal integration and ordered downstream refresh. |
|
Security exact-source review — PASS for Independent checks:
No source finding remains in this bounded mirror-prerequisite correction. This PASS does not transfer implementation/runtime/release authority, does not authorize another pull/build/dispatch, and does not qualify later #1033/#1036 effects. General retains integration ownership. |
Both protected queue attempts for #1033 stopped before tests because the mirror lacked official PHP attestation companion
90503a91…. Pull the canonical immutable indexphp@sha256:3614314e50a9b17a0c317dfd100c6346d8881d6565e713556b7a4e8eb3ec4505through the existing bounded helper, then assign only the local PHP name consumed by the existing build. That index binds the failed companion to its official amd64 runtime/config; the failed jobs did not retain a root-index hash, and none is invented.The sole two-file change has seven focused fake-command controls, accepted policy/isolation checks, full source CI and Security exact-source PASS. It merged normally as
b3388130ab810f46cfaa08de0fd5c9e7bc975f82with the exact reviewed tree. All five actual-main workflows passed (14 successful provider jobs, six intended skips); owned branch/worktree cleanup is complete. Full acceptance receipt.No local image acquisition/build/container, manual dispatch, registry/alias/Release, settings or production action occurred. The selected #1033 refresh now follows this accepted prerequisite.