zac
I’m relatively new to Ash – that said, it seems there are warnings popping up stemming from Ash. After adding a couple of Ash modules, I’m getting:
warning: the Inspect protocol has already been consolidated, an implementation for Walker.Sprint.ActivityStereotype has no effect. If you want to implement protocols after compilation or during tests, check the "Consolidation" section in the Protocol module documentation
lib/walker/sprint/resources/activity_stereotype.ex:1: Walker.Sprint.ActivityStereotype (module)
warning: the Inspect protocol has already been consolidated, an implementation for Walker.Sprint.ActivityStereotype has no effect. If you want to implement protocols after compilation or during tests, check the "Consolidation" section in the Protocol module documentation
lib/walker/sprint/resources/activity_stereotype.ex:1: Walker.Sprint.ActivityStereotype (module)
Compiled lib/walker/sprint/resources/activity_stereotype.ex
warning: the Inspect protocol has already been consolidated, an implementation for Walker.Sprint.Activity has no effect. If you want to implement protocols after compilation or during tests, check the "Consolidation" section in the Protocol module documentation
lib/walker/sprint/resources/activity.ex:1
warning: the Inspect protocol has already been consolidated, an implementation for Walker.Sprint.Activity has no effect. If you want to implement protocols after compilation or during tests, check the "Consolidation" section in the Protocol module documentation
lib/walker/sprint/resources/activity.ex:1
After a bit of research, I’m stumped as to what it means, and what to do about it. One pair of warnings for every new module (entity) that I’m creating. Which is leading to a lot of warnings. Anyone have a clue how to curtail these things?
I’m using Elixir 1.15.7 and Ash 2.17.4.
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
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.
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!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
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)
zachdaniel
I think you can resolve this in dev by not consolidating protocols in dev mode, only in test and production.
zac
Thanks @zachdaniel … Did a little digging and found the Protocol docs mentions that consolidation isn’t used in development (because code reloading), but does happen during compilation. You are right, adding this to the subproject:
And then blowing away
_buildand.elixir_lsfollowed by a clean compile appears to have made the warnings go away. At least in dev.shotleybuilder
@zac thanks for posting. Ran into this error following the ‘Helpdesk’ example on the Ash landing page.
EDIT: Weirdly, having just fired up my 2nd Ash app, this time integrated with phoenix I didn’t get the error …