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

[Bug][claude_code] Incremental collection stops after the first run

未关闭
#9,289 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

@clementsen 已经在做这个了。

开始于 2026年10月30日。

  • #9290 来自 @clementsen —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
32/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go

调研方向

The fix lives around CollectorStateManager (which persists since) and computeUsageDateRange in the Claude Code blueprint collector; grep those symbols to find where the range is computed against the 3-days-behind until. Read the state-manager tests for the existing since semantics, then decide how to record the last collected day rather than the run start. Note that an open pull request (#9290) already targets this issue, so check its state before starting work; done means a second run at least a day later collects the days the first run did not.

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

描述

What happened

After the first successful run, incremental runs collect no data, but they still report success.

Cause

CollectorStateManager saves the start time of the run as since. computeUsageDateRange resumes at since + 1 day, but until is 3 days behind now, so every later run gets an empty range. A plain start = since fix still skips days whenever a run is missed.

Expected

Each incremental run resumes from the last day the previous run collected.

How to reproduce

Run a Claude Code blueprint twice, at least a day apart. The second run collects no new days.

主要语言
Go
星标
3.2k
派生
832
平均合并
2 天 6 小时
30 天内合并 PR
62

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

apache/devlake 的其他 Issue

查看 apache/devlake 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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