-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing stacktraces from right-side effect of .flatMap
#8747
Labels
Comments
/bounty $100 I would expect to see |
💎 $100 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio! |
@jdegoes just want to add a requirement to this ticket if possible? Fixing this can negatively impact performance of the runloop depending on the implementation. I'm actually not sure if it's even possible to fix it without impacting performance to some degree. I thin any attempted solution should either :
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When watching @adamw's recent talk where he compares the usability of direct-style approaches to plain ZIO, I was a bit surprised to see that he argued that ZIO's stacktraces are only "basic". In particular, I was surprised about ZIO's behaviour in this example.
I experimented a bit to understand the behaviour better and found that the stacktrace only contains the "frames" of the left-hand side of a
flatMap
. Here is an example to show the issue:This prints:
which includes the helpful info on where the effects where constructed.
Here is the example where we do not get helpful output:
which prints
I am not sure if this behaviour is intentional, but I agree that this is not ideal from a usability standpoint, because we are missing valuable information to locate the failed effect.
The text was updated successfully, but these errors were encountered: