You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This example does not terminate, it just spins forever.
I beleive this is because StackTraceCleaner does not implement any kind of hard limit (which is the only way I can think of of how to fix this).
I know this is a very specific edge case, it came up while trying to test code that does a similar thing (traverse a Throwable's causes) with a malicious/very broken implementation of a Throwable.
The text was updated successfully, but these errors were encountered:
As a workaround, you can pass -Dcom.google.common.truth.disable_stack_trace_cleaning=true to the JVM when running your test. However, I wonder if you'll then see a failure when your test runner tries to output the exception :) But maybe it will at least overflow the stack and terminate, rather than hanging?
We may try to have a look "eventually." I guess it's at least reasonably straightforward to set a hard limit, as you say.
Example
This example does not terminate, it just spins forever.
I beleive this is because StackTraceCleaner does not implement any kind of hard limit (which is the only way I can think of of how to fix this).
I know this is a very specific edge case, it came up while trying to test code that does a similar thing (traverse a Throwable's causes) with a malicious/very broken implementation of a Throwable.
The text was updated successfully, but these errors were encountered: