Unblocks novox, which is refusing its whole declaration.
mesh-controller#259 fixes while-stopped to name the container as the machine knows it — distribution.store, not store. That fix is built and the declaration names it, but the deployed controller keeps reverting to an older build that still composes the broken form, so every push is refused and the fix cannot land through the normal path.
Taking the step out makes the declaration acceptable to any controller, old or new. Once the fixed controller is deployed and stays, the step goes back.
REGISTRY_STORAGE_DELETE_ENABLED stays — it is already applied on the machine and is harmless on its own.
The step does not come back without its window. A collect step with no while-stopped would run garbage collection against a live registry, which can sweep a blob a concurrent build is pushing. Half of this feature is worse than none of it.
**Unblocks novox, which is refusing its whole declaration.**
mesh-controller#259 fixes `while-stopped` to name the container as the machine knows it — `distribution.store`, not `store`. That fix is built and the declaration names it, but the deployed controller keeps reverting to an older build that still composes the broken form, so every push is refused and the fix cannot land through the normal path.
Taking the step out makes the declaration acceptable to *any* controller, old or new. Once the fixed controller is deployed and stays, the step goes back.
`REGISTRY_STORAGE_DELETE_ENABLED` stays — it is already applied on the machine and is harmless on its own.
**The step does not come back without its window.** A `collect` step with no `while-stopped` would run garbage collection against a live registry, which can sweep a blob a concurrent build is pushing. Half of this feature is worse than none of it.
mesh-controller#259 fixes while-stopped to name the container as the machine
knows it — `distribution.store`, not `store`. Until that controller is the
one composing, novox refuses its whole declaration and takes nothing at all.
The step comes out; deletion stays on, already applied and harmless on its
own. A collect step without its window would be worse than none: garbage
collection against a live registry can sweep a blob a build is pushing.
Put back once the fixed controller is deployed and stays.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Unblocks novox, which is refusing its whole declaration.
mesh-controller#259 fixes
while-stoppedto name the container as the machine knows it —distribution.store, notstore. That fix is built and the declaration names it, but the deployed controller keeps reverting to an older build that still composes the broken form, so every push is refused and the fix cannot land through the normal path.Taking the step out makes the declaration acceptable to any controller, old or new. Once the fixed controller is deployed and stays, the step goes back.
REGISTRY_STORAGE_DELETE_ENABLEDstays — it is already applied on the machine and is harmless on its own.The step does not come back without its window. A
collectstep with nowhile-stoppedwould run garbage collection against a live registry, which can sweep a blob a concurrent build is pushing. Half of this feature is worse than none of it.