Reports: crash/error fingerprint so duplicates group, and Report issue searches before opening a new one

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃

调研方向

Start with fingerprint() in apps/desktop/src/lib/errors/report.ts:442 and the in-session dedupe in errors.svelte.ts:60, then trace how ErrorReport/Diagnostics serialize the Rust crash file. Compare that with the "Report issue" flow in ErrorPanel.svelte (~:160) and the manual dedupe in docs/labels.md. Done means the Rust and TS fingerprints match on the real value (contract test), the same function at different lines yields the same fingerprint, and the search URL is offered before a new issue is opened.

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

描述

area: cli area: desktop priority: 2 normal status: confirmed type: feature

Roadmap item (tracking: #289). From a read-only code audit at main (9c32731); key claims re-checked in code where marked verified. [INFERENCE] = not observed at runtime.

Problem

fingerprint() (apps/desktop/src/lib/errors/report.ts:442) only dedupes toasts in-session (errors.svelte.ts:60); issueUrl carries none; "Report issue" (ErrorPanel.svelte ~:160) always opens a new issue; Rust crash files have no fingerprint; docs/labels.md dedupes by hand.

Proposal

One fingerprint computed in Rust (normalized message + first app frame), serialized through ErrorReport/Diagnostics, written in crash files and issue bodies; "Report issue" first offers issues?q=<fingerprint>.

Acceptance

  • Rust and TS fingerprints match (contract test on the real value); same function at different lines -> same fingerprint; search offered before new issue.
主要语言
Rust
星标
3
派生
1
平均合并
9 小时 51 分钟
30 天内合并 PR
310

环境准备

从这里开始

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

codeatlasdev/atlas 的其他 Issue

查看 codeatlasdev/atlas 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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