anthonator
Hey all!
I’m receiving this dialyzer error from a library and I’m not sure how to suppress it on my end.
lib/core/distributed_registry.ex:17:callback_type_mismatch
Type mismatch for @callback init/1 in Horde.Registry behaviour.
Expected type:
{:ok, Keyword.t()}
Actual type:
:ignore
| {:ok,
{%{:intensity => _, :period => _, :strategy => _}, [any()]}
| %{
:delta_crdt_options => %{:max_sync_size => _, :shutdown => _, :sync_interval => _},
:distribution_strategy => _,
:keys => _,
:listeners => _,
:members => _,
:meta => _
}}
| {:stop, {:bad_return, {atom(), :init, _}}}
________________________________________________________________________________
done (warnings were emitted)
Halting VM with exit status 2
Thanks in advance!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
al2o3cr
Crossreferencing DynamicSupervisor and Registry init spec is wrong. · Issue #181 · elixir-horde/horde · GitHub here for other readers.
We use Horde.Registry and have this same issue, ended up adding a
.dialyzer_ignore.exscontaining:anthonator
Awesome! Thank you!
I ended up putting this at the top of my registry.
thousandsofthem
In similar cases
@dialyzer { :nowarndoesn’t help much - indeed it does suppress the warning, except any function that uses that function will produce the warning instead. This means either i close my eyes on a few dozen of such warnings across the project or mark every single use with nowarn bandaid, making dyalyzer essentially half-useless. Fixing a library would be the solution, but could be not possible for various reasonsanthonator
There’s only so much you can do if you don’t control the code. In this case a fix has been merged but not released.