Skip to content

feat(crash): Rust crash-capture core (panic hook + commands)#691

Merged
fixcik merged 4 commits into
masterfrom
feat/crash-reporting-phase1
Jun 15, 2026
Merged

feat(crash): Rust crash-capture core (panic hook + commands)#691
fixcik merged 4 commits into
masterfrom
feat/crash-reporting-phase1

Conversation

@fixcik

@fixcik fixcik commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Фаза 1 локального crash-reporting (Refs #687). Чистое Rust-ядро, без UI.

Что внутри

  • panic hook (install_panic_hook) — чейнится к дефолтному (вывод в консоль сохраняется), один раз резолвит app_data_dir/crashes и move-захватывает в замыкание, пишет обезличенный crash-record. Сам не паникует (ошибки игнорирует).
  • Хранилище<seq>.json в app_data/crashes (переживает очистку кеша): запись (seq id = max+1), чтение с сортировкой по id, пометка reported/dismissed.
  • Редакция путей — абсолютная домашняя папка → /Users/<user>; относительные source-пути остаются. Применяется при записи, чтобы в публичный issue не утекли локальные пути.
  • 5 Tauri-командlist_pending_crashes, report_frontend_crash, mark_crash_reported, dismiss_crash, build_crash_report (собирает обезличенный markdown, обрезает backtrace под лимит URL GitHub).

Тесты

cargo test -- crash:: — 4 теста (редакция путей ×3, round-trip storage). clippy -D warnings чисто.

Дальше (отдельными PR)

  • Фаза 2 — frontend-захват (ErrorBoundary + window.onerror + breadcrumb).
  • Фаза 3 — UX отправки (старт-промпт, пункт меню, tauri-plugin-opener, i18n).

Дизайн и план — в docs/superpowers/ (локально).

@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@fixcik, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 minutes and 6 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: e773a170-5cf1-4821-872a-200663758074

📥 Commits

Reviewing files that changed from the base of the PR and between a4b79fd and 2d4c000.

📒 Files selected for processing (3)
  • cuprum-ui/src-tauri/src/commands/crash.rs
  • cuprum-ui/src-tauri/src/commands/mod.rs
  • cuprum-ui/src-tauri/src/main.rs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@fixcik fixcik enabled auto-merge (squash) June 15, 2026 23:34
@fixcik fixcik merged commit 7e71353 into master Jun 15, 2026
4 checks passed
@fixcik fixcik deleted the feat/crash-reporting-phase1 branch June 15, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant