$ the-wire · showcase
hf-mount duration defaults silently ignored, funes update now bumps integrations
By RepoJournal · Filed · About Hugging Face · Composed from the cited sources · methodology
Two hf-mount fixes correct behavior that had quietly run on wrong defaults, while funes makes `funes update` cover integrations it used to leave behind.
fix(setup): give xet-core duration defaults a unit so they apply huggingface/hf-mount
The two xet-core duration defaults set in `init_tracing` never actually applied: humantime rejects a bare number, so `HF_XET_CLIENT_READ_TIMEOUT=30` was silently ignored in favor of the 300 s default, and the prefetch target stayed at 15 minutes instead of 30 s, with the WARN hidden under the default `hf_mount=info` filter. Adding units makes both take effect, so reads get a 30 s inactivity tim...
fix(prefetch): keep file offsets when the seek window is first filled huggingface/hf-mount
`PrefetchState::drain_to_seek` treated an empty seek window as contiguous with the forward buffer, so a first drain mid-file left `seek_start` at 0 while holding bytes from elsewhere and a later read near the start of the file got the wrong data. With `FOPEN_KEEP_CACHE` the wrong pages then stuck in the kernel page cache, so if you mount with that flag, restart rather than trust cached pages.
Also recall from unpushed local memory turns huggingface/funes
Recall used to fetch only from a bound remote memory, ignoring locally indexed turns that had not been pushed yet; it now includes those pending local turns in the recallable set, typically at session start and end.
feat(update): bring installed integrations forward huggingface/funes
`funes update` replaced the binary and nothing else, so installed integrations moved only when their agent was re-added: a box stayed on claude/codex/pi 1.0.0 with 1.1.0 in the catalog. It now fetches each installed integration by the same rules `add` follows and re-runs setup only when files changed, leaving anything pinned with `--from` alone.
{kernel,nix}-builder: remove the `cxx11` ABI tag from Linux builds huggingface/kernels
The `cxx11` ABI tag is gone from Linux builds, since Torch fully switched to the C++11 ABI and kernels works untagged as of 0.13; the client still parses variants with and without the tag for existing kernels. Elsewhere today, the kernels card no longer documents private modules, and a funes test asserts that a warm recall resolves to symlinks with zero bytes downloaded.
