Skip to content
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

Fix Elixir 1.11 Warnings #18

Merged
merged 1 commit into from
Aug 25, 2021
Merged

Fix Elixir 1.11 Warnings #18

merged 1 commit into from
Aug 25, 2021

Conversation

djthread
Copy link
Contributor

@djthread djthread commented Nov 7, 2020

During compilation, I get the warnings below repeatedly. It seems to be because we need to have :crypto and :public_key the :extra_applications config.

warning: :crypto.strong_rand_bytes/1 defined in application :crypto is used by the current application but the current application does not directly depend on :crypto. To fix this, you must do one of:

  1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: :crypto]] to your "def project" in mix.exs

  lib/oauther.ex:151: OAuther.nonce/0

warning: :public_key.pem_decode/1 defined in application :public_key is used by the current application but the current application does not directly depend on :public_key. To fix this, you must do one of:

  1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: :public_key]] to your "def project" in mix.exs

  lib/oauther.ex:105: OAuther.decode_private_key/1

@jrissler
Copy link
Contributor

@lexmag are you maintaining this anymore? I'd love to see some of the recent PR's merged in

@lexmag lexmag merged commit eae2a9b into lexmag:master Aug 25, 2021
@lexmag
Copy link
Owner

lexmag commented Aug 25, 2021

Thank you, @djthread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants