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
Fix error message bubbling up on seed error #3248
Conversation
Thanks! Could you add unit test for that? |
Hi Igor, Sure, this behavior is not trivial, but I'll try to come up with something. |
Alright, I've added a straightforward test, which fails on master but passes on this branch. Error output on master:
Error output on this branch:
PS: tests seem to be quite broken on the past few pull requests, is it something to be worried about? |
@risseraka There are some flaky Oracle tests, these are to be ignored, anything else - I'd need to check that out :) |
Thanks a lot for your contribution! |
You're very welcome, thanks for your and every contributor's hard work. (Impressive speed by the way. 😅) |
My pleasure! |
@kibertoad No worries, there's absolutely no urgency, it was just a bit annoying to look at logs on errors, so it's mostly cosmetic, take your time to release whenever you see fit. |
Released in 0.18.0-next1 |
Thanks for the heads up. |
Problem: When the nth seed
throw
s an error, all subsequent seeds add an error message on top of original message which makes it less clear which seed the error originated from.Solution: Nest promises and
catch
error inside the nested seed promise.Before:
After:
LMKWYT,
Cheers.