benwilson512
Hey folks!
I’ve got a branch in Absinthe that conditionally uses the :persisten_term module if it’s available. Unfortunately this is causing me issues with dialyzer, for reasons I can’t quite sort out. I’d like to do one of two things:
- Figure out why dialyzer things
:persistent_term.put/2is unavailable on OTP 21.2. This would be the best option. - If that fails, mark the function as
nowarn. I’ve tried this, but I can’t seem to get the invocation correct.
Branch: Persistent Term Backend by benwilson512 · Pull Request #895 · absinthe-graphql/absinthe · GitHub
Failing Travis job: Travis CI
Line where I try to tell dialyzer to ignore stuff: Persistent Term Backend by benwilson512 · Pull Request #895 · absinthe-graphql/absinthe · GitHub
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
Our Sponsors
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kip
Sometime in the past, for reasons I don’t recall (but I think i was heading down the same path as you) I added the following to my
.dialyzer_ignore_warningsfie which seemed to quiet things down. Hope it helps make some progress.I think this may also have been because of the
@dialyzerissue you are having - i think I had the same but can’t fully recall.benwilson512
Hi @kip thanks for the suggestion. I added a file with those lines to that file and at first it didn’t work, but then switched it to using the Elixir formatted documented by
dialyxir. This worked!Commit: Persistent Term Backend by benwilson512 · Pull Request #895 · absinthe-graphql/absinthe · GitHub
Dialyxir format: GitHub - jeremyjh/dialyxir: Mix tasks to simplify use of Dialyzer in Elixir projects. · GitHub
I’d still like to sort out why dialyzer doesn’t think persistent_term.put exists for that version of Erlang though.
tristan
We’ve now hit this issue in OpenTelemetry Fix dialyzer issues by davydog187 · Pull Request #82 · open-telemetry/opentelemetry-erlang-api · GitHub
But what is extra weird is that dialyzer has been working fine, no warnings about
persistent_term:put/2. It is only now that Elixir’s dialyxer task has been added that its use of dialyzer warns about the function…