Repository navigation
Fix @ProfileConnection stack depth showing filtered and null frames - #289
Merged
jeanbisutti merged 1 commit intoOct 19, 2026
Merged
jeanbisutti merged 1 commit into
jeanbisutti merged 1 commit into
Conversation
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
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.
Problem
With
@ProfileConnection(displayStackTrace = true, stackDepth = N), the stack traces could show frames that the stack trace filters had removed, andnulllines.For example, a JUnit 5 test with
stackDepth = 10printed this forprepareStatement(JDK 17, connection id replaced):With the fix, it prints only the test method frame, as with the default depth:
With
stackDepth = 143in the same test, thegetConnection()stack trace showed the 7 expected frames, then 132 JDK reflection, JUnit, QuickPerf extension and Surefire frames, then 4nulllines.Cause
StackTrace.formatWithfirst applies the filters, which compute the range of elements to keep:QuickPerfStackTraceTraceFiltermoves the start past the QuickPerf frames.limitTothen applied the stack depth.