Issue 108: the registry has no garbage collection, and two doors make it harder to add #91

2026-09-23T21:32:42Z

jschoubben commented

2026-09-23 21:32:42 +00:00

From the review of the registry's public-door conversion. The predecessor ran a stop → garbage-collect → restart routine on a timer; the mesh's registry never had one and the conversion carried the settings but not the routine. With the public door as a second process on the same filesystem, GC now needs two writers stopped, and the mesh has no vocabulary for a maintenance window over several containers. Disk grows without bound. Asks whether the module system needs a maintenance step, what retention means for a mesh that names images by digest, and who owns the routine.

From the review of the registry's public-door conversion. The predecessor ran a stop → `garbage-collect` → restart routine on a timer; the mesh's registry never had one and the conversion carried the settings but not the routine. With the public door as a second process on the same filesystem, GC now needs two writers stopped, and the mesh has no vocabulary for a maintenance window over several containers. Disk grows without bound. Asks whether the module system needs a maintenance step, what retention means for a mesh that names images by digest, and who owns the routine.

jschoubben added 1 commit 2026-09-23 21:32:42 +00:00

Issue 108: the registry has no garbage collection, and two doors make it harder to add 73091dcb4c

jschoubben merged commit 6f173a7912 into main

2026-09-23 21:32:53 +00:00

jschoubben deleted branch issues/108-registry-gc

2026-09-23 21:32:53 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#91