Sentry: render top-level/threads stacktraces, auto-open code frame, clean app:/// paths#286
Merged
butschster merged 2 commits intoJun 9, 2026
Conversation
added 2 commits
June 8, 2026 15:09
Message events (PHP captureMessage with attach_stacktrace, some JS SDKs) carry their trace at the top level or under threads, which the exception view never read, so they showed no stacktrace. resolveExceptionValues now synthesizes an exception from that trace. The frame list also auto-opens the first frame with source code (then the first in_app frame) instead of index 0, so JS traces whose innermost frame is a library/anonymous frame no longer render with no code visible.
Sentry's node/RewriteFrames integration normalizes server paths to the app:// scheme with an empty authority, which rendered as a confusing 'app:///+page.server.js' (the path looked collapsed to '///'). Display the clean app-relative path; URLs and node: builtins are unchanged. IDE-link building still uses the raw filename so custom path mappings keep working.
This was referenced Jun 9, 2026
Author
|
i guess the storybook test is something i cannot fix, if i understand the test correctly? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Display-side fixes for the Sentry module, the frontend counterpart to buggregator/server#339. Together they address the v2 long-standing issues in buggregator/server#338 (SvelteKit/JS stack traces "not there, no code read").
What's fixed
threadsstacktraces (31b8306). Message events (and some JS SDKs) attach the stacktrace at the payload top level or underthreads[].stacktracerather thanexception.values[].stacktrace.resolveExceptionValuessurfaces those so the trace renders instead of showing nothing.31b8306). JS traces often put a library/anonymous frame on top; opening frame 0 showed no code. Open the first frame that carries source (then the firstin_appframe), so the relevant code is visible by default.app:///node paths (6146339). Sentry's node/RewriteFrames normalizes server paths to theapp://scheme with an empty authority, rendering as a confusingapp:///+page.server.js(the path looked collapsed to///). Show the clean app-relative path; URLs andnode:builtins unchanged; IDE-link building still uses the raw filename so custom path mappings keep working.Related