Skip to content

sync: open-core source for 0.2.3 - #53

Merged
prabod merged 3 commits into
mainfrom
sync/source-0.2.3-efda25f9
Aug 19, 2026
Merged

sync: open-core source for 0.2.3#53
prabod merged 3 commits into
mainfrom
sync/source-0.2.3-efda25f9

Conversation

@prabod

@prabod prabod commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Source sync for 0.2.3, generated by tools/sync_public.py from the engine tree
at e8a1fa11, plus hand-written docs the allow-list does not cover.

Commits

  • sync: — generated. Allow-listed paths only; tuned quantization profiles and
    internal tooling are excluded by rule.
  • docs: — hand-written. docs/ is outside the allow-list.
  • sync: (refresh) — regenerated after the resumable-downloads and
    catalog-scanner changes landed internally.

Contents

  • base-convert/crates/base-hub: Xet support and a parallel, resumable
    downloader (download.rs), the catalog scanner (scan.rs), and fetch.rs
    ported to hf-hub 1.0. base-hub/Cargo.toml adds indicatif and reqwest.
  • catalog.json: regenerated from the published organization — 69 rows → 105,
    adding every Whisper bundle and Qwen3.8-27B, and correcting eight rows whose
    size/sha256 no longer matched the Hub.
  • Version mirrors to 0.2.3: public header, Swift header, binding manifests,
    package.json, setup.py, __init__.py.
  • Docs: Rust floor 1.85+, the BASERT_HF_* variables, and a "How downloads
    behave" section in the models guide.

Notes

  • Per-crate Cargo.toml files are newly allow-listed. Without them this PR would
    publish fetch.rs/download.rs against a manifest declaring neither
    dependency, and the tree would not compile.
  • Downloads resume by default. Xet is opt-in via BASERT_HF_XET; it
    deduplicates across models but cannot resume an interrupted transfer.
  • Rust 1.85 is required: hf-hub 1.0 is edition 2024.

Verified in this branch

check result
cargo build --locked --workspace clean
cargo test --workspace 262 passed, 0 failed
cargo clippy --all-targets -- -D warnings clean

baseRT sync and others added 2 commits August 19, 2026 10:24
Generated by tools/sync_public.py from the internal tree at efda25f9.
Only allow-listed paths are included; tuned quant profiles and internal
tooling are excluded by rule.
Hand-written to accompany the generated sync; none of these paths are in
the allow-list, so `tools/sync_public.py` cannot carry them.

- Rust 1.85+ in both places that state the floor. hf-hub 1.0 is edition
  2024, so 1.80 is now a hard build failure and these two pages are what a
  new user follows.
- The five `BASERT_HF_*` download knobs, in the table that already
  documents the rest of the environment.
- A "How downloads behave" section in the models guide, because the
  transport is now user-visible.

The resume paragraph says exactly what was measured, which is not the
tidier claim: a ranged download resumes from its chunk map, a Xet download
restarts from the beginning. Killed at 2246 MiB, a Xet pull came back 12s
into its next attempt with 328 MiB — a restart, and hf-hub 1.0 exposes no
way to hand hf-xet a chunk cache that would change it. Readers planning an
overnight pull on a bad link need that difference, and `FORCE_RANGED` is
the lever it implies.
@prabod
prabod marked this pull request as draft August 19, 2026 01:00
@prabod

prabod commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

Holding as draft: the internal 0.2.3 tag is on hold while basert pull is made resumable on the Xet path (today only the ranged path resumes). This sync will be refreshed from the final tree before it merges, so the docs and the code land describing the same behavior.

Regenerated from the internal tree at e8a1fa11, which carries two changes
that landed after this branch was first written:

  * downloads are resumable by DEFAULT — the parallel ranged path is now
    what every large file takes, and Xet is opt-in behind BASERT_HF_XET,
    because Xet cannot resume;
  * the catalog is generated by scanning the published org rather than
    hand-written: 69 rows -> 105, adding every Whisper bundle and
    Qwen3.8-27B, and correcting eight rows whose size/sha256 no longer
    matched the Hub (those four models could not be pulled at all).

New file: base-hub/src/scan.rs, plus the `catalog-scan` command.

The hand-written docs follow the same change: the environment table now
documents 24 x 16MB defaults and BASERT_HF_XET in place of the removed
BASERT_HF_FORCE_RANGED, and the models guide states plainly that a pull
resumes, with Xet described as the deduplicating alternative that does
not.

Verified in this tree: cargo build --locked --workspace clean,
cargo test --workspace 262 passed, clippy clean under -D warnings.
@prabod
prabod marked this pull request as ready for review August 19, 2026 03:30
@prabod
prabod merged commit 0644388 into main Aug 19, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant