ReSkate

0 Fork 0

mirror of https://github.com/Dingo-Shenanigans/ReSkate.git synced 2026-10-17 20:57:08 +02:00

Files

T

History

AyeZeeBB 571d57f603 Crash reports: sent as envelopes so their logs arrive, with the log's last lines, crash site and mods

Sentry's minidump endpoint streams every attachment but the dump to an object store, which this
self-hosted Sentry does not run: ReSkate.log and report.json were dropped from every crash
(outcome upload_failed). Each crash now goes to the envelope endpoint as sentry-native sends one:
the event, the minidump, report.json and the log, all kept.

- The event carries the log's last 100 lines as breadcrumbs (debug lines only among the last 25),
  the mods the game ran with (enabled, outdated, excluded), how long it had run, and an anonymous
  install ID as its user. Its time is the crash's, however late it is sent.
- crash.site tags where it crashed ("Skate.exe+0x3d9ed9d"), as Sentry names game code by the
  nearest export; mods.count how many mods were on.
- An accepted report is kept in sent/ (the newest 10) instead of deleted, so the player still has
  their crashes.
- multipart.* is report_envelope.*; the receipt check also reads the envelope endpoint's
  {"id": ...}.

2026-10-16 17:59:40 -05:00

Test

Crash reports: sent as envelopes so their logs arrive, with the log's last lines, crash site and mods

2026-10-16 17:59:40 -05:00

client.cpp

Crash reports: the game's own fatal crashes come with the memory their stacks point at

2026-10-15 20:01:55 -05:00

crash_report.h

Crash reports: the game's own fatal crashes come with the memory their stacks point at

2026-10-15 20:01:55 -05:00

native_dump.cpp

Crash reports: self-hosted Sentry instead of Backtrace, and opt-in performance timings