-
Notifications
You must be signed in to change notification settings - Fork 30
Work around missing function support #44
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
Conversation
We can expand on this a bit? I don't believe Elixir nor the Erlang VM actually supports compiling on a newer OTP version. You should always compile on the lowest version that you plan to support. |
|
@dominicletz is there feedback you can provide to Jose, as we're also in need of this PR for LVN |
|
Yes, sorry it's the other way around. E.g. compiling on an older version then the newer functions become not accessible even when running on a new OTP. I've fixed that comment. And yes OTP supports running older beam code on newer OTP releases. I think two major release steps are supported. The one exception here is |
|
Sorry, it is still unclear what is going on here. There are two possibilities:
I'd like to break this apart, perhaps as two separate PRs? The ones for number 1 above we can definitely merge. Thanks. |
|
I've created a new PR just with the hash_equals fallback https://github.com/elixir-plug/plug_crypto/pull/45/files |
|
Thank you, it has been merged. Please let me know if this is enough to squash iOS issues. |
|
We'll try this today on our end. Thank you |
|
|
|
New package is out. |
|
Thanks @dominicletz! If the other patch is ready, let me know, but given that it is about OTP 24, we should be fine. :) |
This fixes two issues:
crypto.hash_equals can be present but unsupported (in which case it throws)
When compiling beam files on an older otp revision than deploying , the compile time detection reports false positives. Instead we're using runtime detection now always.