b1az
I’m still getting "a previous clause at line 1 always matches" warning below, even though I long ago removed the .ex file that was re-defining the problematic DefineMessage module from exprotobuf:
> mix deps.compile
> mix compile
==> my_app
Compiling 13 files (.ex)
warning: this clause cannot match because a previous clause at line 1 always matches
lib/exprotobuf/define_message.ex:1
This was indeed a valid warning for this project, as it used to contain a same-named module DefineMessage. The module was in a file under config/, and on deployment it would overwrite exprotobuf’s own module: we’d literally do
cp config/our_define_message.ex \
deps/exprotobuf/lib/exprotobuf/define_message.ex
A similar issue on GitHub was supposedly already resolved.
In despair, grep from the project root, with grouped output between .elixir_ls/, _build/ and deps/:
> grep -R DefineMessage .
Binary file ./.elixir_ls/dialyzer_tmp/.elixir_ls/build/_test/lib/exprotobuf/ebin/Elixir.Protobuf.Builder.beam matches
Binary file ./.elixir_ls/dialyzer_tmp/.elixir_ls/build/_test/lib/exprotobuf/ebin/Elixir.Protobuf.DefineMessage.beam matches
./.elixir_ls/build/_test/lib/exprotobuf/ebin/exprotobuf.app: 'Elixir.Protobuf.DefineMessage',
Binary file ./.elixir_ls/build/_test/lib/exprotobuf/ebin/Elixir.Protobuf.Builder.beam matches
Binary file ./.elixir_ls/build/_test/lib/exprotobuf/ebin/Elixir.Protobuf.DefineMessage.beam matches
Binary file ./_build/dev/lib/my_app/.mix/compile.app_tracer matches
./_build/dev/lib/exprotobuf/ebin/exprotobuf.app: 'Elixir.Protobuf.DefineMessage',
Binary file ./_build/dev/lib/exprotobuf/ebin/Elixir.Protobuf.Builder.beam matches
Binary file ./_build/dev/lib/exprotobuf/ebin/Elixir.Protobuf.DefineMessage.beam matches
grep: ./deps/setup/xtest/testapp-2/rebar: No such file or directory
grep: ./deps/setup/xtest/testapp-1/rebar: No such file or directory
./deps/exprotobuf/lib/exprotobuf/define_message.ex:defmodule Protobuf.DefineMessage do
./deps/exprotobuf/lib/exprotobuf/builder.ex: import Protobuf.DefineMessage, only: [def_message: 3]
Any ideas where the issue might lie much appreciated.
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
So i have been using ash framework for a while and i love it. However currently the issue im having with ash framework is the error handl...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex











Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
patfranciso
Try
$ mix clean
before
$ mix compile
b1az
Thanks for the suggestion. Alas, neither
mix cleannormix clean --depsworked.mix clean --depsseems to delete_build/$MIX_ENV. I even triedrm -rf deps/ _build/before in vain. Open to further suggestions, I need to get rid of this last warning.PS. Recloned the project, ran
rm -rf .git _build depsand recompiled. Still, the warning persists.Maybe unrelated, but even with elixir set to 1.10.4 via
asdf……
elixir --versionstill returns1.11.2.axelson
Maybe you’ve installed something as a global archive? Also something appears to be incorrect in your asdf setup if the incorrect version is being used. Does
asdf currentalso show 1.10.4? What doeswhich -a elixirshow?b1az
Thanks for the help Jason. I’ve looked further into both areas you mention, global archives and asdf.
Global archive
I think these are the only global archives.
asdf v0.8.0
asdf currentlooks ok.List of all
elixirexecutables ok as well.And the content of the above shim.
Worth noting that I also ‘fixed’ the
syntax error before: "$@"issue with asdf’smixshim and changed~/.asdf/shims/mixfromto a ‘working’ version.
factoryd
I’ve had this happen quite a bit and removing the ElixiLS directory always resolves it.
rm -rf ./.elixir_lsb1az
Thanks. Alas, even
didn’t resolve this warning.
ericmj
Can you share the project or a project that reproduces the issue so that we can take a look?
b1az
Yes, will try to reproduce in a sample project. If that fails, I’ll try to get an approval from the stakeholders.
avix990
I’m having a similar issue with one of my projects, where one of the types modules for Absinthe, is returning me this error:
I have tried all the steps mentioned above, but the error persists.
mfilej
Same issue here on the
TypesGraphQL module (use Absinthe.Schema.Notation).