Triage: #42 "Export to CSV crashes"
Recommendation: category bug, state needs-info. The issue is unlabeled now. The normal path is needs-triage first, but I think it can go straight to needs-info. Either way, the label change and comment wait for your go-ahead.
What I checked
- Prior rejection: there is no
.out-of-scope/directory, so there is no earlier rejection to surface. - Redundancy: this is a crash report, not a feature request, so an existing implementation doesn't apply.
- Codebase: I couldn't explore it. The working directory isn't a git repo, and I only have a file reader here, with no way to list directories or search. I didn't want to guess at paths. If you tell me where the reports page and its export handler live, I'll trace the code path.
- Reproduction: not attempted. There's no running app or repro data, and the report has no steps I could follow.
Why needs-info
The report is too thin to reproduce or to write a durable agent brief from:
- "Spins forever, then the page goes blank" could be a hung request or a server timeout. It could also be an unhandled client-side exception or a memory blowup on a large dataset.
- "Happens on my laptop" gives no browser, OS or app version.
- It doesn't say whether the export works for smaller reports, other reports or other users.
Draft comment (not posted)
> *This was generated by AI during triage.*
## Triage Notes
**What we've established so far:**
- Clicking Export on the reports page shows a spinner that never finishes, then the page goes blank.
- Reported on the reporter's laptop only; we haven't seen it elsewhere yet.
**What we still need from you (@sam):**
- Which report were you exporting, and roughly how many rows does it have? Does a smaller report or a narrower date range export fine?
- Which browser and version are you using, and which OS?
- Open the browser dev tools (Console and Network tabs) and click Export again. Is there a red error in the Console? Does the export request show a status code, or stay "pending"? Please paste what you see.
- Does it fail every time, or only sometimes? Does it also fail for a teammate or on another machine?
- Which app version or deploy are you on?
Next step: should I apply bug + needs-info and post that comment? Or would you rather go to needs-triage first, or give me the code location so I can try to verify the crash from the source before asking @sam anything?
How it was tried: I installed triage together with the grilling and domain-modeling skills it can call, in a clean temporary folder, and invoked it as a slash command with one pasted issue and no issue tracker connected. Only Skill and Read tools were allowed, so nothing was posted, labelled or closed, the codebase could not be explored and no bug was reproduced. It shows only the recommend step and a drafted comment, and it stops to wait for your go-ahead.
它做什么
给维护者用的工作流。它让每个议题（以及每个外部 PR，视为带代码的议题）走过两类角色（bug、enhancement）和五个状态（needs-triage、needs-info、ready-for-agent、ready-for-human、wontfix）。
工作方式
- 列出需要关注的：未打标签的、
needs-triage的、以及needs-info且有新回复的。 - 针对一个条目：完整读一遍，检查该行为是否已经实现，并查看
.out-of-scope/里有没有以前拒绝过的类似请求。 - 给出分类和状态的建议，然后等你的指示。
- 验证说法是否成立：复现缺陷，或确认 PR 的确做了它声称的事。
- 需要细化时，进行一轮
grilling+domain-modeling。 - 落实结果：写任务说明、写待补充信息的说明，或附上解释后关闭。自带的两份指南讲怎么写经得起时间的代理任务说明，以及
.out-of-scope/知识库的用法。
适合场景
议题很多的项目维护者。它会发评论、也能关闭议题，请逐项确认它要做的动作。
高风险：它会操作你的议题系统：打标签、发评论（每条都以"由 AI 生成"的声明开头）、关闭议题。遇到缺陷或外部 PR 时，它可能复现缺陷，或拉取 PR 代码并运行其中的测试，也就是会运行你没有审过的代码，处理不可信的 PR 请用沙箱或干净的克隆目录。它还会向仓库写入文件（`.out-of-scope/`，以及术语表、ADR 的更新）。它的设计是先给出建议、等你指示再执行，但批准前请逐条看清它要做的动作。需要你的议题系统标签映射，以及 `grilling` 和 `domain-modeling` 两个 Skill。 已试用一次：只贴了一个议题，没有连接议题系统，也没有写文件和命令行工具，只观察到了推荐分类和起草评论这一步。没有发评论、打标签或关闭议题，也没有复现缺陷或拉取 PR。