-
-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown dialyzer warning option: race_conditions with OTP 25.0.4 #470
Comments
Yes OTP removed support for this feature. I don't think there is really anything we can do other than remove it from the documentation. |
Thanks for the info @jeremyjh . I haven't checked. Do you want some help to remove these references from the documentation? |
Sure, a PR is welcome! |
Thanks one more time @jeremyjh.. I'm closing this issue. |
w0rd-driven
added a commit
to w0rd-driven/beatseek
that referenced
this issue
Jan 27, 2023
Postgres: attempt using the official image. I haven't done this enough to know honestly and I may need a docker login regardless. Dialyzer: No longer supports `race_conditions`: jeremyjh/dialyxir#470. Unknown is included by default I believe so there's no need to include it again. Add MP3Stat exclusions tied to the line numbers. If I drastically change this file I need to follow the warnings too. I'm fine with making this whitelist as I don't think Beatseek had these checks applied or they may have taken different approaches.
w0rd-driven
added a commit
to w0rd-driven/beatseek
that referenced
this issue
Mar 21, 2023
Postgres: attempt using the official image. I haven't done this enough to know honestly and I may need a docker login regardless. Dialyzer: No longer supports `race_conditions`: jeremyjh/dialyxir#470. Unknown is included by default I believe so there's no need to include it again. Add MP3Stat exclusions tied to the line numbers. If I drastically change this file I need to follow the warnings too. I'm fine with making this whitelist as I don't think Beatseek had these checks applied or they may have taken different approaches.
w0rd-driven
added a commit
to w0rd-driven/beatseek_private
that referenced
this issue
Jul 11, 2023
Postgres: attempt using the official image. I haven't done this enough to know honestly and I may need a docker login regardless. Dialyzer: No longer supports `race_conditions`: jeremyjh/dialyxir#470. Unknown is included by default I believe so there's no need to include it again. Add MP3Stat exclusions tied to the line numbers. If I drastically change this file I need to follow the warnings too. I'm fine with making this whitelist as I don't think Beatseek had these checks applied or they may have taken different approaches.
w0rd-driven
added a commit
to w0rd-driven/beatseek
that referenced
this issue
Jul 11, 2023
Postgres: attempt using the official image. I haven't done this enough to know honestly and I may need a docker login regardless. Dialyzer: No longer supports `race_conditions`: jeremyjh/dialyxir#470. Unknown is included by default I believe so there's no need to include it again. Add MP3Stat exclusions tied to the line numbers. If I drastically change this file I need to follow the warnings too. I'm fine with making this whitelist as I don't think Beatseek had these checks applied or they may have taken different approaches.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Elixir & Erlang/OTP versions (elixir --version):
Which version of Dialyxir are you using? (cat mix.lock | grep dialyxir):
Current behavior
To demostraste this behaviour I have create an application through the command
mix new dummy_app
and havingmix.exs
withdialyxir
like that:as feedback of the command
mix dialyzer
I got the error :dialyzer.run error: Unknown dialyzer warning option: race_conditionsExpected behavior
If I change to using OTP 24 instead I'm able to run the dialyzer successfully
The text was updated successfully, but these errors were encountered: