Closed cecton closed 8 years ago
Hi @cecton, thanks for raising this.
parbolied, a library scala-uri depends on was calling printStackTrace()
on the exception, however this has been fixed in https://github.com/sirthias/parboiled2/issues/145
I have updated to the latest parboiled and it seems to have fixed the issue. This is published as a new version 0.4.15
of scala-uri.
Try it and let me know it goes.
Yeay! It works, many thanks!
Hello,
I spent quite a lot of time trying to understand why I still get the traceback in the stdout/stderr despite I'm wrapping the call in a Try(). I just don't get it and I can't see anything in scala-uri that could possibly print this traceback.
You can reproduce it simply by using a Scala interpreter:
As you can see x is still being defined with a Failure instance, this is totally what I expect. But I just can't get rid of the traceback for some reason. I'm having this traceback during tests also (even if all the test passed).
Here I don't see any traceback. Why is it different?
I'm a beginner in Scala so I understand this issue can be due to a mistake of myself, but any hint would be really appreciated.
Thanks for your help