-
Notifications
You must be signed in to change notification settings - Fork 42
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
Crash on Application startup with String.to_existing_atom
#85
Comments
hello! thanks for the report. What version oif Elixir and Erlang OTP are you running? |
Otp 26, elixir 1.15 |
I see, yea I have not done any testing around that yet. it s related to the change they added in 1.15 . https://hexdocs.pm/elixir/1.15/changelog.html#potential-incompatibilities . Can you try this in your project and see if that helps? |
+1, getting the same error on a fresh install of Hammer 6.2 on Elixir 1.15.6 and OTP 26 |
Tried this, did not help. Looking at the code I don't see where these atoms are getting instantiated prior to String.to_existing_atom/1 call |
@arjan I am (edit:)ALMOST able to bypass this bug by changing my hammer config :hammer,
backend: {
Hammer.Backend.ETS,
[
expiry_ms: 60_000 * 60 * 2,
cleanup_interval_ms: 300_000 * 2
]
} because single-backend config uses a single static default pool atom, HOWEVER when I do this I run into the following error when trying to call Hammer:
new issue opened #88 |
Hammer.Supervisor
fails to start because it assumes the hammer backend names already exist in the atom pool.Easily reproducible with running the following in
iex
:Crashes in the following way:
The text was updated successfully, but these errors were encountered: