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
In #191 it was introduced a debug trace to show the stack trace when a context error was suppressed, it is really nice to find out places that neede to be corrected, except it is doesn't work as expected, this is the trace it produces: [LogErrorContextMissingStrategy] java.lang.RuntimeException: Failed to end subsegment: subsegment cannot be found.
The throwable should be the second param and a message should be added as the first param, otherwise, Apache logging just calls toString on the first param to get the message.
The text was updated successfully, but these errors were encountered:
In #191 it was introduced a debug trace to show the stack trace when a context error was suppressed, it is really nice to find out places that neede to be corrected, except it is doesn't work as expected, this is the trace it produces:
[LogErrorContextMissingStrategy] java.lang.RuntimeException: Failed to end subsegment: subsegment cannot be found.
The throwable should be the second param and a message should be added as the first param, otherwise, Apache logging just calls toString on the first param to get the message.
The text was updated successfully, but these errors were encountered: