honeybadger-elixir
honeybadger-elixir copied to clipboard
honeybadger-io
Phoenix.Router.NoRouteError being reported
Hello,
For some reason, HoneyBadger is sending Phoenix.Router.NoRouteError errors even when I inserted my use Honeybadger.Plug after the use CoreWeb, :router call.
Phoenix version: 1.5.3 Honeybadger version: 0.15
Here is a screenshot of the error in the HoneyBadger dashboard:
Feel free to ask me for any more information needed.
Oh, I just noticed that it seems that HoneyBadger is also accumulating a lot of different errors with that one for some reason:
Seems like that because of that ErlangError title, HoneyBadger is thinking every error with this same title is the same error.. If this is another issue let me know and I will create a separate issue for it.
@sezaru I have tried reproducing the error with the phoenix and honeybadger version specified. Still, I'm unable to get the bug you are facing. Kindly confirm with me the Elixir and Erlang versions that you are using.
@joshuap , I have seen that there was a fix for this bug that was released in version 0.11, any ideas on this one?
@joshuap , I have seen that there was a fix for this bug that was released in version 0.11, any ideas on this one?
I'm not sure to be honest, but @sorentwo might have input. This issue does look similar to this old one: https://github.com/honeybadger-io/honeybadger-elixir/issues/130
Something in those error messages looks wrong. They're all generic erlang errors stacked three levels deep like they are wrapped. I wouldn't expect the default filter to match on those based on how they're structured, but I admit that I don't know why they're formatted that way.
The problem is that on my end everything seems to be working fine, it could be at least easier if we could reproduce the same error.
I think the formatting was also handled if I'm not wrong .
Thanks, everyone. Let's keep this open a while longer to see if anyone can provide additional data to reproduce. I'm fine with closing it in a few weeks, otherwise.