fix: rework database dump workflow#419
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The weekly dump zipped the per-table JSON into a single release asset, which now exceeds GitHub's 2 GiB per-asset cap (~23 GB raw -> ~2 GB zip). Rather than dropping tables (the #418 stopgap, which breaks anyone rebuilding the DB from the dump), tar the dump, compress with xz/lzma2 (preset=9e, 192 MiB dict), and split into <2 GiB parts. split always emits >=1 part, so consumers use one uniform 'cat parts | xz -d | tar -x' flow. xz -9e is CPU-bound, so run the job on a 32-vCPU Blacksmith runner to stay within the 30-min cap. Update README + inferencex-data skill consumer docs to match. dump-db.ts/load-dump.ts unchanged (still a plain JSON dir).
adibarra
force-pushed
the
fix/db-dump-xz-split
branch
from
0d0d751 to
cf39c78
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Operational and documentation change only; consumers must switch from zip to the new unpack steps, but application code and DB access are unchanged.
Overview
Replaces weekly DB release packaging from a single
.zipwith xz-compressed tar archives split into ~1.9 GiB.tar.xz.part*files, so dumps can grow past GitHub’s per-asset size limit while keeping full table dumps intact.The Database Dump workflow now runs on
blacksmith-32vcpu-ubuntu-2404, usesset -euo pipefail, pipestar→xz(lzma2) →split, and attaches all parts to the release via an expanded glob. README and the inferencex-data skill document the new download pattern (gh+cat … | xz -d | tar -x) and the simplifiedDUMP_DIRexample path after unpack.Reviewed by Cursor Bugbot for commit cf39c78. Bugbot is set up for automated code reviews on this repo. Configure here.