Wrapper Logs don't parse correctly when a STDOUT message follows a stacktrace with the same timestamp

[Joshlha]

Whenever we get to a new line in a wrapper log, the logic does this:

• Check to see if it has a logger level (the first letter after the timestamp, like W or I or D or whatever)
  • If it does, it's a new log event
  • If not, we check to see if it has the same timestamp as the previous log event
    • If it's the same timestamp as last, it gets treated as another line of a stacktrace.

Whenever we have an error with a stacktrace, if a STDOUT message appears with no log level flag for us to check, we are currently assuming that it is part of the previous event's stacktrace.

Currently not sure how we'd get around this, but likely some sort of loose regex or something which guesses if we have a stacktrace line or not.

[paul-griffith]

Hmm

Yeah, this could in theory be done, though I wonder how common this actually is out in the wild