Issue report feature - #43
Conversation
A Report an Issue sheet, opened from the sidebar footer, collects a category (model download, model inference, app UI, app interaction, crash), a description, and optional diagnostics: app and system info, model and server settings, category-specific details such as cache disk space, live inference metrics, or recent crash reports, plus an optional server-output tail. The report is previewed in full, copied to the clipboard, and opened as a prefilled GitHub issue; nothing is sent anywhere until the user submits it on GitHub.
The sidebar's Report an Issue button now builds the diagnostics report and opens a prefilled GitHub new-issue page to review and submit there, instead of a separate in-app form. Uses a bug icon; removes the unused report view.
|
LGTM, just a couple nits:
|
|
yeah, seems like a categorical design is best for which bugs users want to report, I'll address that and second issue! edit: done! |
- Report an Issue is now a category menu; each choice collects that category's diagnostics (disk, metrics, or crash reports) and applies the matching label instead of every report being App interaction. - When a report exceeds the URL budget, the full body is copied to the clipboard before truncation, and the truncated Markdown closes any open code fence or <details> block so it still renders.
2 participants
Way to report issues in nativ's gb repo's issue page.
Once clicked, opens a prefilled GitHub new-issue page populated with app/runtime diagnostics, server and model state, and recent log lines (home directory redacted) for the reporter to review and submit along with description of issue.