serve.zone/onebox
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 82 Wiki Activity

82 Releases 305 Tags

RSS Feed
  • v33.17.2 dddd12ed07
    Compare

    Onebox v33.17.2
    Release / build-and-release (push) Failing after 24m9s
    Details
    Stable

    philkunz released this 2026-10-14 21:44:40 +00:00 | 2 commits to main since this release

    2026-10-14 - 33.17.2

    Fixes

    • Pin the platform Corestore 32.2.7 by its multi-platform image index code.foss.global/serve.zone/corestore@sha256:73ebbfecc33f52022249bbbbdaef331c31b8bfaf3cd2de23cf58b874ef821334 (linux/amd64 and linux/arm64), moved from 32.2.5 (sha256:a6a702f04320e15198a16a309dd939af927d3bcd74d14d92b0ce3f44526a3e7d) in ts/platform-images.ts, and declare it as oneboxCorestorePinnedRelease 32.2.7. Corestore 32.2.7 is a maintenance release of the 32.2 line that serves object storage from @lossless.org/objectstorage 10.7.1 instead of 10.3.1 (through 32.2.6, which brought 10.7.0): reads no longer queue behind bucket listings. A listing held the engine-wide object gate while it walked and sorted the whole bucket, so every GET and HEAD on every bucket waited for it; a listing now holds a per-bucket gate that blocks only writes to the bucket it lists, the engine-wide object migration gate is held only for the legacy-layout reconciliation before the walk, and the walk covers only the keys its prefix and cursor reach. On central this removes the 6–25 s registry read stalls that pushed Cloudly deploy preflights past their deadlines. Through 10.7.0 workloads also get CopyObject read authorization on the source, durable staged writes, UploadPartCopy and disabled Nagle's algorithm (Corestore 32.2.6 changelog). The NoSQLDB engine stays 10.10.0 and the object layout is unchanged, so 32.2.5 to 32.2.7 adds no one-way step: 32.2.5 serves a pool 32.2.7 wrote, and the movers' restore to 32.2.5 holds. One rollback condition applies: a write of a new key that a crash interrupts leaves a staged directory in .smartstorage/staging/v1/ that 32.2.5's objectstorage 10.3.1 refuses at startup, so start and stop 32.2.7 once before rolling back to 32.2.5; if 32.2.7 cannot start, back up the root first, then remove only the *.object.tmp.leaf directories there, which hold payloads that were never published (Corestore 32.2.6 changelog). A completed engine conversion keeps running the image its journal names, so after the binary upgrade it still runs 32.2.5 until onebox migration corestore-engine --replace-completed-target-image moves it, and a native owner until --replace-native-target-image does; both admit 32.2.5 to 32.2.7 as a newer release of the same major, read from both images' release labels; the 32.2.7 index states 32.2.7 in its org.opencontainers.image.version and version labels on both platforms. An owner still on 32.2.4 or earlier crosses the one-way first start of NoSQLDB 10.10.0 with this move as it did with 32.2.5, so take a block-level snapshot of its Corestore volume with the services stopped first. The completed-target replacement test now runs the move from the 32.2.5 index with this release's own pin, and the backup exclusion tests run against objectstorage 10.7.1, the engine of the pinned Corestore. The change adds no startup data migration.

    Maintenance

    • release tooling: @git.zone/tstest 8.0.0, @git.zone/tsbundle 3.3.0 (pnpm 12.10.1 and @types/node 26.6.4 stay: pnpm 12.11.2 and @types/node 26.6.5 are younger than the 7-day release-age rule; @git.zone/tsdeno stays 1.15.0 until the binary moves from Deno to a Node single executable application, owner decision 2026-10-14)
    Downloads