<unknown> #3

Activity

1. sentry

   added

   bugSomething isn't workingSomething isn't working

   sentryAuto-created from Sentry crash reportAuto-created from Sentry crash report

   needs-triageAwaiting initial reviewAwaiting initial review

   on Apr 28, 2026
2. codedev-david

   closed this as completedin 1050f8eon Apr 28, 2026
3. codedev-david commented on Apr 28, 2026

   

   codedev-david

   on Apr 28, 2026

   Owner

   More actions

   Fixed in v1.11.24 (commit 1050f8e). Root cause: renderer's unhandledrejection listener was forwarding raw DOM Event objects to Sentry, which can't symbolize them — hence the "Event Event (type=error)" title.

   Fix in src/renderer/src/lib/sentry.ts:

   • Real Error instances pass through unchanged.
   • DOM Events with a target are wrapped in an Error capturing the event type + target tag + src/href.
   • Empty 'error' Events with no target are dropped (the case that produced this issue).
   • Strings/objects/null are coerced into properly-messaged Errors.

   8 new unit tests in tests/renderer/sentry.test.ts cover the matrix.
4. codedev-david

   added 2 commits that reference this issue on Jun 30, 2026

   v1.16.7: memory hardening — observable recall, live-session freshness…

   ...

   3757d64

   docs(README): lead with the shared-memory-that-learns moat

   ...

   4724be3
5. codedev-david

   added a commit that references this issue on Oct 12, 2026

   fix(paste): send pastes through xterm so a long paste lands whole

   ...

   971ac37