-
-
Notifications
You must be signed in to change notification settings - Fork 336
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
src/ranch_ssl.erl:137: ssl:ssl_accept/3: deprecated; use ssl:handshake/3 instead #195
Comments
Please instead review #194 which is what we'll move toward while approaching Ranch 2.0. The warning in question can just be disabled. Note that your solution is incorrect because ssl:handshake's return value is different. |
I'm guessing you get an issue with rebar and warning_as_errors set in your project preventing compilation? |
Same error:
I compile ranch under erlang version 21, and this is the error msg. |
Yes, these two functions return different results. The solution is wrong. |
I know it doesn't compile by itself under 21 but Ranch is used as a dependency and Erlang.mk disables warning_as_errors for dependencies so this has little impact on users, it compiles for them. I'm asking about rebar because to prevent future problems I can generate a rebar.config that will disable warning_as_errors for rebar too, and then we can separately ignore that warning. |
How about this:
The function returns the same result now. |
We've added the warning disabling to the PR I mentioned. It'll be merged when I'm less busy with other things. |
Closing, thanks! I also confirmed that it did NOT produce an error when used with rebar3 as a dependency, only a warning. If it was producing an error with an other tool, please let me know. |
There is a solution for this, but I don't know how to use it with erlang.mk
copy from joedevivo/chatterbox#127
The text was updated successfully, but these errors were encountered: