-
-
Notifications
You must be signed in to change notification settings - Fork 757
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
Most recent call last backtraces #2989
Comments
You're welcome to open a PR adding this feature, note that it will need to be within our notifications that process this to make the backtrace reversible to all formatters. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Subject of the issue
I'm not sure if this is an issue or already configurable or mentioned elsewhere or something, or even if feature requests go elsewhere. So apologies in advance if I need to look elsewhere.
But since ruby 2.5 we get reversed backtraces. I.e. most recent call last.
I did have a quick search but didn't find anything.
I'm a fan of them and keep getting thrown off by now needing to scan to the top and the bottom because of RSpec output versus exception backtraces. sometimes seeing a bit of both depending on the test.
I think overall having the mix of the two is worse than keeping the old most recent first approach.
Your environment
Steps to reproduce
run a failing spec and look at the backtrace. It will be with most recent first.
Expected behavior
If configured reverse the backtrace output to have most recent last.
Actual behavior
Most recent first.
The text was updated successfully, but these errors were encountered: