Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

A podcast refuses on a tight machine rather than voicing at a smaller chunk

未关闭
  • 哪里不对？
#1,982 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@Yogi-cy 已经在做这个了。

开始于 2026年10月5日。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Read the audio.cpp request and session options first to establish how chunk size is configured, then trace check_voicing_memory() in memory.py through _wait_for_memory() and _voice_each() in speech.py. Start with a failing test in test_speech.py; handle models with no chunk_steps and update the catalog documentation. Verify real-model behavior with test_audiocpp_voicing.py and listen to a two-speaker podcast at each enabled step.

由索引模型根据 Issue 内容生成。

描述

desktop enhancement help wanted

The gap

docs/architecture/local-models/catalog.md lists this under Known gaps:

The audio block's chunk_steps are committed but nothing reads them: short of memory at the default chunk, a podcast refuses rather than stepping down, until a listening test clears the smaller chunks.

Why it matters

Kokoro peaks at 2,347 MB while voicing at the default chunk, and at 1,442 MB at 120 characters and 956 MB at 60. Those numbers were measured on audio.cpp v0.8.2, reviewed and committed. A machine with two and a half gigabytes free is refused a podcast it could produce at half the memory, and the refusal instead suggests a different, lighter model — a worse answer than the same model voicing more slowly.

The manifest rule this page states is that an entry carries only fields some engine reads, precisely so nothing is reviewed and trusted while doing nothing. chunk_steps has been that field since it was added, and the memory check is one argument away from using it.

Where

What done looks like

  • A machine short of memory at the default chunk voices at the largest committed step that fits, rather than refusing, and a model with no steps still refuses with the sentence it gives today.
  • The refusal, when it comes, accounts for the smallest step, not the default peak — otherwise the numbers in the message are wrong.
  • The listening test is part of this issue, not a follow-up. Voice a two-speaker podcast at each step you enable and confirm the audio holds up; say in the PR what you listened to and on which audio.cpp build. A step that degrades the audio should not be enabled however well it fits.
  • Delete the Known gaps line from docs/architecture/local-models/catalog.md in the same PR, and update the chunk_steps bullet under The manifest so it describes a field that is read.

How to verify

surfsense_local/backend/tests/unit/llm/providers/audiocpp/test_speech.py drives voicing against a mock transport with an injectable available callable, so every memory branch is a unit test with no audio involved. tests/packaging/test_audiocpp_voicing.py is the real-model harness, gated on SURFSENSE_TEST_AUDIO_MODELS. The repo is TDD: write the failing unit test first.

cd surfsense_local/backend
uv run pytest -m unit
uv run pytest -m integration
uv run ruff check .

Before you start

Read CONTRIBUTING.md, the local model catalog doc and the Studio doc, which owns the podcast job this serves. Say up front whether you can run audio.cpp with a real model; without that the listening test cannot be done and the issue cannot be finished. Open your PR against dev, not main. Comment here to claim this.

主要语言
Python
星标
16.3k
派生
1.6k
平均合并
11 小时 37 分钟
30 天内合并 PR
261

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

MODSetter/SurfSense 的其他 Issue

查看 MODSetter/SurfSense 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。