You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using better_errors, I get no backtraces (and no REPL) for ArgumentError thrown from code. Forcing them with raise works fine.
I traced the problem back to set_backtrace not being called when the ArgumentError is caused by the code, but it is called when the error is forced with raise. The constructor is called in both instances
I saw some patch that added setting the backtrace to both the constructor and set_backtrace, but this code seems to be gone from the current release. Is there a reason for not patching the constructor any more?
Environment
better_errors: 20.10.1
binding_of_caller: 1.0.0
rails: 7.0.7.2
ruby: 3.2.2
arch: arm64 (Mac M1)
The text was updated successfully, but these errors were encountered:
When using better_errors, I get no backtraces (and no REPL) for
ArgumentError
thrown from code. Forcing them withraise
works fine.I traced the problem back to
set_backtrace
not being called when theArgumentError
is caused by the code, but it is called when the error is forced withraise
. The constructor is called in both instancesI saw some patch that added setting the backtrace to both the constructor and
set_backtrace
, but this code seems to be gone from the current release. Is there a reason for not patching the constructor any more?Environment
The text was updated successfully, but these errors were encountered: