pepicrft
Hi 
I’m using Elixir and Phoenix in a new open source project and I noticed that incremental builds are unreliable. Sometimes they work fine, and other times start yielding odd behaviours:
- It fails to compile an external dependency that had previously been successfully compiled.
- It starts compiling all the projects even if I only change one line of code in a file. I checked with
xrefand--sinkand no other module has a compile dependency with it.
My guess is that something is odd in my module graph, but xref is not revealing anything useful. How would you recommend debugging this issue? I was excited about everything Elixir would offer, but incremental builds that often get invalidated worsen the experience significantly.
Edit
I just noticed that the incremental build got invalidated after seeing an error popping in the bottom right corner of VSCode so it might have something to do with either the ElixirLS or Credo extensions.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
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!"
First 5 of 5 Posts
D4no0
Have you tried removing the
_buildfolder?I’ve had it a few times happen to me too, but those are very rare.
hst337
That’s strange. How can I reproduce it?
dimitarvp
I’d start with deleting VSCode’s directory – I think it was
.vscode? – and let it rebuild its stuff first. IIRC it kind of duplicates work with the Elixir LSP and that has been an occasional problem for people but was always solved by pruning the directories so far.D4no0
The elixir-ls uses a custom root directory named
.elixir-ls.I also might have a suspection there might be some kind of version mismatch, are you using
asdforrtxto manage elixir/OTP versions?pepicrft
I’ve disabled the Credo VSCode and that seems to have solved the issue. I wonder if it conflicts with ElixirLS somehow.