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

SSL, dialyzer, applications #1

Open
martinsumner opened this issue Dec 4, 2024 · 2 comments
Open

SSL, dialyzer, applications #1

martinsumner opened this issue Dec 4, 2024 · 2 comments

Comments

@martinsumner
Copy link
Contributor

There have been issues related to dialyzer and the use of SSL in ibrowse.

There appears to be issues if:

  • it is not referred to in app.src;
  • Is added in applications;
  • Is added to included_applications.

Adding it to applications (which was the last change), breaks the use of riak erlang http client in riak_test.

@martinsumner
Copy link
Contributor Author

martinsumner commented Dec 4, 2024

If there is no reference to ssl then OTP 26 dialyzer complains:

src/ibrowse_http_client.erl
Line 580 Column 13: Unknown function ssl:connect/4
Line 590 Column 21: Unknown function ssl:connect/3
Line 659 Column 57: Unknown function ssl:send/2
Line 746 Column 59: Unknown function ssl:close/1
Line 759 Column 50: Unknown function ssl:setopts/2
Line 1356 Column 10: Unknown function ssl:connect/3

Including it though causes issues where ssl is not started in tests.

@martinsumner
Copy link
Contributor Author

The answer appears to be to include in applications and optional_applications

@tburghart tburghart transferred this issue from OpenRiak/ibrowse-forked Feb 4, 2025
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

No branches or pull requests

1 participant