com/18193802/175365039-4aa9f526-f117-432b-ba5d-3a834175d5e2.png
>
>
>
>
> -----Original Message-
> From: Jochen Theodorou
> Sent: Thursday, June 23, 2022 6:32 AM
> To: dev@groovy.apache.org
> Subject: [EXT] Re: StackTrace sanitization list
>
> External Email: Use
ithubusercontent.com/18193802/175365039-4aa9f526-f117-432b-ba5d-3a834175d5e2.png
-Original Message-
From: Jochen Theodorou
Sent: Thursday, June 23, 2022 6:32 AM
To: dev@groovy.apache.org
Subject: [EXT] Re: StackTrace sanitization list
External Email: Use caution with links and attachments
Hi there,
not sure if it helps, but myself, I've played with the sanitizer, and
eventually wrote my own track dumper which does two parts:
- first, it dumps my own code only (plus some extras, e.g., for internally
compiled scripts it shows the offending line, etc.)
- after that, it dumps full st
On 23.06.22 11:41, Paul King wrote:
I tend to agree with you but it does get a little tricky. If "my own
user code" is making use of e.g. Java collection classes, then
sometimes I'd really like to see "one level down".
one level down... well, for you in
[...]
Caught: java.lang.NullPointerExce
I tend to agree with you but it does get a little tricky. If "my own
user code" is making use of e.g. Java collection classes, then
sometimes I'd really like to see "one level down".
Take this example:
///
def list = [null, 'a', 'b', 'c', 'd', 'e', 'f']
assert
For me, sanitization is essentially to hide all the plumbing, and only keep
my own user code on the surface, so that I know where in my code it started
failing.
So I tend to want more sanitization than less :-)
On Thu, Jun 23, 2022 at 3:29 AM Paul King wrote:
> Hi folks,
>
> We've had a recent P
Hi folks,
We've had a recent PR to add "jdk.internal" to the list of packages we
remove when sanitizing stacktraces:
https://github.com/apache/groovy/pull/1727
We've also had a much earlier request to filter less aggressively, see:
https://github.com/apache/groovy/pull/256
https://issues.apache
