solid_errors icon indicating copy to clipboard operation
solid_errors copied to clipboard

Published 20 hours ago • verified publisher icon fractaledmind

Patch the action_dispatch executor to report rendered exceptions

Open fractaledmind opened this issue 1 year ago • 2 comments

Resolves #12

fractaledmind avatar Feb 07 '24 18:02 fractaledmind

Now I'm seeing this:

Puma caught this error: super: no superclass method `call' for #<ActionDispatch::Executor:0x000000010646e310
[...]

holman avatar Feb 08 '24 19:02 holman

I really don't want to have to put a workaround into this gem.

I have finished my investigation and I wrote a detailed explanation of what is happening: https://github.com/rails/rails/issues/51002#issuecomment-1936054456

Takeaway: there is definitely an issue here, and Rails applications will not report errors that occur within the HTTP lifecycle unless reloading is enabled.

Hopefully we can get a resolution in upstream Rails instead of this still-not-working hack.

fractaledmind avatar Feb 09 '24 14:02 fractaledmind