Bug reports: private full log (and opt-in minidump) alongside the public excerpt #738

New issue

Open

opened 2026-10-13 00:55:12 +00:00 by sky_line · 0 comments

sky_line commented

2026-10-13 00:55:12 +00:00

Owner

Design: two tiers

Public excerpt (as now, in the issue): stays readable and safe. Always include the most recent memory / VRAM / pipeline status lines, regardless of the per-location cap and budget.
Private full log (new): the whole current session log, plus the previous session's log when the report follows a crash.
- Scrubbed only for what is actually dangerous: capability URLs and tokens, session ids, IP addresses, avatar / display names. Otherwise complete.
- Compressed (16 MB of log is about 1-2 MB).
- Stored by the relay outside the public tracker. The issue links to it; only maintainers can open it.
- Kept for a fixed period, then deleted (retention to be decided).
- Report Bug shows a checkbox, on by default: "Include full log (private, developers only)".
Minidump: separate checkbox, off by default, explained plainly (it is a snapshot of the viewer's memory and can contain chat text and live session keys). Same private storage.

Notes

Needs relay server changes (private upload store, access control, retention); requires owner approval before deploying.
Report Bug must say plainly what is sent and who can see it.
Size caps and rate limits as for the existing log upload.

Bug reports only carry a filtered log excerpt (render/system/warning sources, at most 192 KB / 1,500 lines, 5 entries per log location, reading the last 4 MB plus the first 1 MB). Reports become **public** issues, so the filtering is needed -- but it regularly drops what we need. #736 (Windows crash enabling RT reflections) arrived with no memory status at all, no stack, and the minidump stuck on the reporter's machine. ## Design: two tiers 1. **Public excerpt** (as now, in the issue): stays readable and safe. Always include the most recent memory / VRAM / pipeline status lines, regardless of the per-location cap and budget. 2. **Private full log** (new): the whole current session log, plus the previous session's log when the report follows a crash. - Scrubbed only for what is actually dangerous: capability URLs and tokens, session ids, IP addresses, avatar / display names. Otherwise complete. - Compressed (16 MB of log is about 1-2 MB). - Stored by the relay **outside the public tracker**. The issue links to it; only maintainers can open it. - Kept for a fixed period, then deleted (retention to be decided). - Report Bug shows a checkbox, on by default: "Include full log (private, developers only)". 3. **Minidump**: separate checkbox, **off by default**, explained plainly (it is a snapshot of the viewer's memory and can contain chat text and live session keys). Same private storage. ## Notes - Needs relay server changes (private upload store, access control, retention); requires owner approval before deploying. - Report Bug must say plainly what is sent and who can see it. - Size caps and rate limits as for the existing log upload.

sky_line added the

feature

triage

labels

2026-10-13 00:55:12 +00:00

sky_line added this to the Slipstream project

2026-10-13 00:55:13 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sky_line/Slipstream#738

No description provided.

Rows
Columns