Hey, sorry for the bump, but could someone look at...
# arrow-contributors
c
Hey, sorry for the bump, but could someone look at the unanswered questions at https://github.com/arrow-kt/arrow/issues/3388?
y
I'll look at this later today. I was the last person to touch this code so probably I can fix it quickly.
c
to clarify—there's a good chance nothing is broken at all, and it's a misinterpretation on my side. I asked a few questions to be sure whether this is the case 🙂
y
So the message itself is definitely expected. It's the default message of a
RaiseCancellationException
. Now that I look at it, yes the message is actually completely expected. I thought a suppressed exception was the issue, but no you're just calling
stackTraceToString
. A decision was made to include the
RaiseCancellationException
message, but perhaps that should be removed. The note on
stackTraceToString
reads:
Note, the first line in the stacktrace will be the RaiseCancellationException. The users call to raise can found in the_second line of the stacktrace.
c
^ I interpreted this as being about the
at:
lines, I wasn't sure whether it also applied to the message.
y
I think however Simon pointed out that a different unexpected behaviour was happening, which I'll take a look at later today then, but yes what's happening to you is entirely expected, although should likely be improved. I think the difficulty is that there's no multiplatform way to inspect the stacktrace That's a fair interpretation. Looking at the impl, it's absolutely just printing the exception with its message and everything.
c
Therefore I can just hide that message from the user, thanks 🙂
👍🏼 1
Then it's official: Prepared is the first test framework with Raise tracing support 😇
😍 3