Repository navigation
ci: commit the DB dump gzipped - #112
Merged
Merged
Conversation
The refresh-dump workflow could no longer push its branch: with the two dictionaries added in forzagreen/arabterm#60 and forzagreen/arabterm#61, db/arabterm.sql is 109.50 MB, over GitHub's limit of 100 MB per file. The dump is now committed as db/arabterm.sql.gz (about 25 MB), the way arabterm commits its own database: - `make download_dump` keeps the downloaded archive and checks it; `make fix_dump` applies its two fixes through a pipe and recompresses with `gzip -n`, so that an unchanged dump gives an unchanged file. - `deploy-db` imports with `gunzip -c db/arabterm.sql.gz | mariadb ...`, after `gzip -t`. - GitHub shows no diff of a gzipped file, so the refresh pull request now states how many SQL lines were added and removed, next to the data summary sent by arabterm. db/arabterm.sql.gz in this commit is the dump that was already committed, byte for byte once unpacked: merging re-imports the same data, which exercises the new import path before any data change.
forzagreen
added a commit
that referenced
this pull request
Oct 7, 2026
…-db (#113) The deploy-db run of #112 failed before importing anything: the bastion checkout had an untracked db/arabterm.sql.gz, which `git pull --ff-only` refuses to overwrite now that the file is tracked. The checkout is only a deploy mirror, so fetch and `git reset --hard origin/main`: a leftover file can no longer block the import. Ignored files (var/) are kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P46G3NWFFqPMVwDmVo4vLJ
forzagreen
added a commit
that referenced
this pull request
Oct 18, 2026
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
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.
The "Refresh DB dump from arabterm" workflow can no longer push its branch: with the two dictionaries added in forzagreen/arabterm#60 and forzagreen/arabterm#61,
db/arabterm.sqlis 109.50 MB, over GitHub's limit of 100 MB per file (failed run). Production is still on the data of arabterm5b421dd.The dump is now committed as
db/arabterm.sql.gz(about 25 MB), the way arabterm commits its own database.Changes
download_dumpkeeps the downloaded archive and checks it withgzip -t;fix_dumpapplies its two fixes through a pipe and recompresses withgzip -n, so an unchanged dump gives an unchanged file. The macOS/Linuxsed -iswitch is gone, since nothing is edited in place any more.curlgets-L(the download URL redirects).ci.yml: thedata/codepath filters follow the new file name;deploy-dbrunsgzip -t, thengunzip -c db/arabterm.sql.gz | mariadb ....refresh-dump.yml: commitsdb/arabterm.sql.gz. GitHub shows no diff of a gzipped file, so the pull request description now states how many SQL lines were added and removed, next to the data summary sent by arabterm.Data
db/arabterm.sql.gzhere is the dump that was already committed, byte for byte once unpacked. Merging therefore re-imports the same data, which exercises the new import path before any data change. The two new dictionaries come with the next refresh pull request (run the workflow by hand after this merge).Tested
make fix_dumpon the committed archive gives the same bytes back.make download_dump && make fix_dumpagainst arabtermmain: a 28 MB archive, nouca1400collation or sandbox line left, and the line count of the new workflow step gives 94472 added, 11 removed (94444 terms, 2 dictionaries, and the dump header lines).