[Feature]: Add disk capacity history to Sysinfo
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 66/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- go, typescript
调研方向
Start by tracing the existing sysinfo event and CPU/memory history implementation, then inspect the gopsutil collection path and the current Plot Type menu. Done means namespaced disk capacity metrics are published in GiB, the Disk Space plot graphs free space against total capacity, focused Go/TypeScript tests cover the behavior, and the custom-widget documentation is updated.
由索引模型根据 Issue 内容生成。
描述
Feature description
The Sysinfo widget currently plots CPU and memory, but it cannot show whether the monitored machine's primary filesystem is running out of capacity. A disk-space plot would make storage depletion visible without leaving Wave, including for remote connections already supported by Sysinfo.
Proposed scope: add a Disk Space plot type showing free capacity in GiB for the primary filesystem, using the existing Sysinfo history and plot UI. This is capacity, not disk I/O throughput.
Implementation suggestion
- Collect primary-filesystem total, used, and free bytes with the existing
gopsutildependency and publish GiB values alongside CPU/memory in the currentsysinfoevent. - Add namespaced metrics such as
disk:space:total,disk:space:used, anddisk:space:freeso future I/O metrics remain distinct. - Add
Disk Spaceto the existing Plot Type menu, graphing free space from zero to total capacity. - Cover collection and plot selection with focused Go/TypeScript tests and document the new custom-widget plot type.
I am ready to submit the focused implementation if this direction and naming align with Wave's product direction.
Anything else?
This request is based on the existing CPU + Mem Sysinfo widget in Wave 0.14.5. The goal is the same native graph surface, not a terminal/TUI workaround.
- 主要语言
- Go
- 星标
- 22.4k
- 派生
- 1.1k
- 平均合并
- 12 天 6 小时
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
wavetermdev/waveterm 的其他 Issue
-
pwsh: encodeEnvVarsForPowerShell rejects Windows-standard env var names like ProgramFiles(x86), breaking wsh token on every pwsh block可能已有人在做 @vortsghost2025 于 25 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
wavetermdev/waveterm#3481 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
wavetermdev/waveterm#3435 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
wavetermdev/waveterm#3432 ·
维护者通常 1 天内回复
-
enhancement triage
难度 2/5 1-3 小时 新手友好度 82/100
wavetermdev/waveterm#3431 ·
维护者通常 1 天内回复
-
[Bug]: web blocks become unresponsive when switching focus between two of them可能已有人在做 @jameswolensky 于 83 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
wavetermdev/waveterm#3428 ·
维护者通常 1 天内回复
查看 wavetermdev/waveterm 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 86/100
modelcontextprotocol/go-sdk#1340 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
seccomp: goToNative values for loong64 and mipsle have no matching nativeToSeccomp key可能已有人在做 @ricardobranco777 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
native-convergence self-host
难度 2/5 1-3 小时 新手友好度 86/100
JakeChampion/lang#11408 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1445 ·
维护者通常 2 天内回复