Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Logging: full AppHandle Debug dump on every line of transcribe_audio (≈96% of log size)

未關閉
#2,367 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
68/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
rust, tauri

研究方向

Start at the Rust transcribe_audio entry point and inspect its #[instrument] fields, the per-chunk resampling logs, and the System audio dropping frames warning. Check the RollingFileAppender configuration for the filename suffix. Done means AppHandle data is excluded from routine events, chunk and unchanged-drop logs are less noisy, and generated daily log filenames end in .log.

由索引模型根據 Issue 內容生成。

描述

bug
Description

The transcribe_audio span includes app: AppHandle without skip, so every event inside it
prints the full AppHandle Debug output (~9 KB: Tauri config, CSP, plugin list, state TypeIds...).
Combined with per-chunk INFO logging during resampling (Processing chunk N /
Successfully resampled chunk N, 818 lines for one 14-min file), a single transcription attempt
produced a 7.7 MB log: 950 lines, 837 of them with the dump. Without the dumps it's 322 KB.

Suggested:
  • #[instrument(skip(app))] on transcribe_audio (and any other command taking AppHandle).
  • Per-chunk progress at DEBUG/TRACE, or one progress line per N%.
  • Minor: daily log files are named cap-desktop.log.2026-09-28; macOS doesn't treat them as
    logs (no Console.app double-click). RollingFileAppender::builder().filename_suffix("log")
    would give cap-desktop.2026-09-28.log.
  • Minor: System audio dropping frames WARN is repeated every 5 s even when the drop counter
    hasn't changed.
Additional Context
  • Cap version: 0.6.0
  • Operating system, version: 26.2 (25C56)
  • Device (optional): Macbook M1

cap-desktop-2.log

主要語言
Rust
星號
22.8k
分支
2k
平均合併
12 小時 41 分鐘
30 天內合併 PR
84

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CapSoftware/Cap 的其他 Issue

查看 CapSoftware/Cap 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。