Repository navigation
Bump transformers floor past 5.17.0 to unblock VibeVoice; Bark breakage acceptable #224
Description
Split from #190/#169 — dependency-floor change, gated on Don's explicit call: Bark is expendable (see #190, #), so the transformers>=5.16.1,!=5.17.0 exclusion from #169 (which exists only to protect Bark's generate_speech default path from a TextToAudioPipeline.preprocess BatchEncoding.to(dtype=...) bug in 5.17.0) no longer needs to hold this repo back.
Ask: move the transformers floor to a release that both contains VibeVoice and is otherwise current — verify on lem first (pip index versions transformers / check changelog) which release VibeVoice landed in (5.17.0 per #190's research) and whether later releases fix or reintroduce the Bark bug. Bark itself is being replaced as the default TTS (see follow-up ticket), so a regression to Bark under the new floor is not a blocking concern for this ticket — just note it in the fix comment so the tester doesn't spend time chasing it as a regression against #169.
Depends on / enables: #190 (chat-templated messages input plumbing for generate_speech) needs this floor bump before its VibeVoice path can be verified for real rather than only probed for graceful rejection.
Activity
dkackman commentedon Sep 18, 2026
triage: batch with #224, #225 — #225 depends on #224, both land in
dw/tasks/speech_generation.py/pyproject.toml, one pip upgrade + restart on lem; #224's session does both. Fact that changes #224's shape: PyPI's newest transformers is 5.17.0 (pip index versions transformers, 2026-09-18) — there is no release "past" it to move to, so the fix is to drop the!=5.17.0exclusion (floor>=5.17.0,pyproject.toml:46), accept that Bark's defaultgenerate_speechpath regresses (#169's bug, now Don's accepted cost, #226 replaces the default), and say so plainly in the hand-off so the tester doesn't chase it. Check what lem actually has installed before upgrading, and confirmVibeVoiceclasses import on the installed build (they do on 5.17.0 locally). Then #225:messageskwarg passed astext_inputs, relaxtask.py:515totextORmessages, the four edge cases in the issue, docs + mocked tests. Live VibeVoice verification is the tester's, after deploy. No new validation surface — one optional argument on an existing task with a documented guard.— triage by the implementer agent running as model
opusvia theanthropicprovider.fix(tests): #224 - stop pinning diffusers' private cache-context inte…
fix(tests): #224 - stop pinning diffusers' private cache-context inte…
dkackman commentedon Sep 18, 2026
Fixed the CI failure directly. `PR #228`'s `backend` job failed 4 tests in `tests/test_cache_blocks.py` - unrelated to the transformers floor bump itself, but exposed by it re-running CI at a moment when diffusers' upstream `main` (installed fresh from git on every run, per `.github/workflows/ci.yml`) had renamed/reworded some of its private cache-context internals (`StateManager._current_context`, `HookRegistry._set_context`, and `StateManager.get_state`'s error text) that those 4 tests pinned directly instead of going through the public contract.
Both verified: `pytest tests/test_cache_blocks.py` (17 passed) and the full suite (5092 passed, 16 skipped) locally, plus green `backend` CI on #229's PR.
Along the way, found and filed #231 (unrelated): `ruff` bumped to 0.16.7 on `develop` and now wants to reformat 16 unrelated files - pre-existing drift, not blocking this, ported past it with an admin merge on #230.
Closing.
fix(deps): #232 - revert transformers floor to >=5.16.1,!=5.17.0
Develop (#241)