Add :public_key to extra_applications #3

Closed

minibikini wants to merge 0 commits from gitlab-mr-iid-1 into master

pull from: gitlab-mr-iid-1

merge into: pleroma-elixir-libraries:master

pleroma-elixir-libraries:master

pleroma-elixir-libraries:bump/version-0.1.3

pleroma-elixir-libraries:akkoma-real-world-fixtures

pleroma-elixir-libraries:gitlab-mr-iid-10

pleroma-elixir-libraries:refetch_public_key-guard

pleroma-elixir-libraries:gitlab-mr-iid-9

pleroma-elixir-libraries:gitlab-mr-iid-6

pleroma-elixir-libraries:gitlab-mr-iid-7

pleroma-elixir-libraries:mix-lock

pleroma-elixir-libraries:gitlab-mr-iid-5

pleroma-elixir-libraries:2022-03-deps

pleroma-elixir-libraries:gitlab-mr-iid-4

pleroma-elixir-libraries:gitlab-mr-iid-3

pleroma-elixir-libraries:release/0.1.1

pleroma-elixir-libraries:gitlab-mr-iid-2

pleroma-elixir-libraries:fix/public-key-warnings

Conversation 0 Commits - Files changed -

minibikini commented 2020-11-17 18:45:50 +00:00

Member

Copy link

Fixes compilation warnings:

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

Found at 3 locations:
  test/support/test_adapter.ex:11: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:17: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:21: HTTPSignatures.TestAdapter

warning: :public_key.pem_entry_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

Found at 3 locations:
  test/support/test_adapter.ex:15: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:18: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:23: HTTPSignatures.TestAdapter

warning: :public_key.sign/3 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/http_signatures/http_signatures.ex:87: HTTPSignatures.sign/3

warning: :public_key.verify/4 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/http_signatures/http_signatures.ex:37: HTTPSignatures.validate/3

Fixes compilation warnings: ``` 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 Found at 3 locations: test/support/test_adapter.ex:11: HTTPSignatures.TestAdapter test/support/test_adapter.ex:17: HTTPSignatures.TestAdapter test/support/test_adapter.ex:21: HTTPSignatures.TestAdapter warning: :public_key.pem_entry_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 Found at 3 locations: test/support/test_adapter.ex:15: HTTPSignatures.TestAdapter test/support/test_adapter.ex:18: HTTPSignatures.TestAdapter test/support/test_adapter.ex:23: HTTPSignatures.TestAdapter warning: :public_key.sign/3 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/http_signatures/http_signatures.ex:87: HTTPSignatures.sign/3 warning: :public_key.verify/4 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/http_signatures/http_signatures.ex:37: HTTPSignatures.validate/3 ```

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

pleroma-elixir-libraries/http_signatures!3

No description provided.