-
Notifications
You must be signed in to change notification settings - Fork 455
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
error message "logger:remove_handler(default) failed" printed at startup #507
Comments
@notslang yes, this is due to fact that Elixir is also removing
|
This is a bit late, but I ran into the same thing; there is another potential fix for this mentioned at the bottom of the amqp client page. You need to add def application do
[
extra_applications: [:lager, :logger, :amqp]
]
end Hope this is useful. |
Was seeing `calling logger:remove_handler(default) failed: :error {:badmatch, {:error, {:not_found, :default}}}` when running tests. According to a GitHub issue[1], the fix is to start `lager` before `logger`. [1]: erlang-lager/lager#507 (comment)
For what it's worth, none of the above worked for me. I'm using Elixir 1.12 / OTP 24. And this dependency overwrites the logger configuration. When running |
Tried this: erlang-lager/lager#507 (comment) Co-authored-by: Kaz <[email protected]>
I found a small issue where upgrading amqp_client from
3.7.13
to3.7.14
causes an error message to be printed when I start up my Elixir application:The error is being printed due to code introduced by this change, since lager is a dependency of amqp_client and was upgraded as a result of upgrading amqp_client. However, I have no idea if this is a defect in lager or if it's another dependency using lager incorrectly, and I'm not sure how to check.
I'm using Erlang/OTP 22, if that helps.
Is this the right place to report this?
The text was updated successfully, but these errors were encountered: