b72a46db68
Some checks failed
Update All Top Ranking Issues / update_top_ranking_issues (push) Has been cancelled
Triage Project Sync (#84) / Sync triage project (push) Has been cancelled
release_nightly / notify_on_failure (push) Has been cancelled
release_nightly / check_style (push) Has been cancelled
release_nightly / run_tests_windows (push) Has been cancelled
release_nightly / clippy_windows (push) Has been cancelled
release_nightly / bundle_linux_aarch64 (push) Has been cancelled
release_nightly / bundle_linux_x86_64 (push) Has been cancelled
release_nightly / bundle_mac_aarch64 (push) Has been cancelled
release_nightly / bundle_mac_x86_64 (push) Has been cancelled
release_nightly / bundle_windows_aarch64 (push) Has been cancelled
release_nightly / bundle_windows_x86_64 (push) Has been cancelled
release_nightly / build_nix_linux_x86_64 (push) Has been cancelled
release_nightly / build_nix_mac_aarch64 (push) Has been cancelled
release_nightly / update_nightly_tag (push) Has been cancelled
Hotfix Review Monitor / check-hotfix-reviews (push) Has been cancelled
Stale PR Review Reminder / check-stale-prs (push) Has been cancelled
Update Weekly Top Ranking Issues / update_top_ranking_issues (push) Has been cancelled
Bump collab-staging Tag / update-collab-staging-tag (push) Has been cancelled
compliance_check / scheduled_compliance_check (push) Has been cancelled
Single-commit orphan branch: full zed-industries/zed @ 8c74db0 source tree with a 3-file patch applied (no upstream history). Patch (crates/gpui_linux/src/linux/wayland/): - serial.rs: add SerialKind::KeyboardEnter - client.rs: store wl_keyboard.enter serial; add latest_serial_of() - window.rs: activate() uses keyboard-enter serial (Mutter focus gate) Mutter honors window activation only when the token carries the keyboard- focus serial from wl_keyboard.enter; GPUI used a stale mouse-press serial. See docs/tray-window-focus-wayland.md in logiguard. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
90 lines
2.6 KiB
Markdown
90 lines
2.6 KiB
Markdown
# Crash Issue Linking
|
|
|
|
You are linking a crash to potentially related GitHub issues so human reviewers can quickly validate whether a fix may resolve multiple reports.
|
|
|
|
## Inputs
|
|
|
|
Before starting, you should have:
|
|
|
|
1. **Crash report** (from `script/sentry-fetch <issue-id>` or Sentry MCP)
|
|
2. **ANALYSIS.md** from investigation phase, including root cause and crash site
|
|
|
|
If either is missing, stop and report what is missing.
|
|
|
|
## Goal
|
|
|
|
Search GitHub issues and produce a reviewer-ready shortlist grouped by confidence:
|
|
|
|
- **High confidence**
|
|
- **Medium confidence**
|
|
- **Low confidence**
|
|
|
|
The output is advisory only. Humans must confirm before adding closing keywords or making release claims.
|
|
|
|
## Workflow
|
|
|
|
### Step 1: Build Search Signals
|
|
|
|
Extract concrete signals from the crash + analysis:
|
|
|
|
1. Crash site function, file, and crate
|
|
2. Error message / panic text
|
|
3. Key stack frames (especially in-app)
|
|
4. Reproduction trigger phrasing (user actions)
|
|
5. Affected platform/version tags if available
|
|
|
|
### Step 2: Search GitHub Issues
|
|
|
|
Search **only** issues in `zed-industries/zed` (prefer `gh issue list` / `gh issue view` / GraphQL if available) by:
|
|
|
|
1. Panic/error text
|
|
2. Function/file names
|
|
3. Crate/module names + symptom keywords
|
|
4. Similar reproduction patterns
|
|
|
|
Check both open and recently closed issues in `zed-industries/zed`.
|
|
|
|
### Step 3: Score Confidence
|
|
|
|
Assign confidence based on evidence quality:
|
|
|
|
- **High:** direct technical overlap (same crash site or same invariant violation with matching repro language)
|
|
- **Medium:** partial overlap (same subsystem and symptom, but indirect stack/repro match)
|
|
- **Low:** thematic similarity only (same area/keywords without solid technical match)
|
|
|
|
Avoid inflated confidence. If uncertain, downgrade.
|
|
|
|
### Step 4: Produce Structured Output
|
|
|
|
Write `LINKED_ISSUES.md` using this exact structure:
|
|
|
|
```markdown
|
|
# Potentially Related GitHub Issues
|
|
|
|
## High Confidence
|
|
- [#12345](https://github.com/zed-industries/zed/issues/12345) — <title>
|
|
- Why: <1-2 sentence evidence-backed rationale>
|
|
- Evidence: <stack frame / error text / repro alignment>
|
|
|
|
## Medium Confidence
|
|
- ...
|
|
|
|
## Low Confidence
|
|
- ...
|
|
|
|
## Reviewer Checklist
|
|
- [ ] Confirm High confidence issues should be referenced in PR body
|
|
- [ ] Confirm any issue should receive closing keywords (`Fixes #...`)
|
|
- [ ] Reject false positives before merge
|
|
```
|
|
|
|
If no credible matches are found, keep sections present and write `- None found` under each.
|
|
|
|
## Rules
|
|
|
|
- Do not fabricate issues or URLs.
|
|
- Do not include issues from any repository other than `zed-industries/zed`.
|
|
- Do not add closing keywords automatically.
|
|
- Keep rationale short and evidence-based.
|
|
- Favor precision over recall.
|