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

CI OTP 24 #229

Merged
merged 6 commits into from
May 28, 2021
Merged

CI OTP 24 #229

merged 6 commits into from
May 28, 2021

Conversation

paulo-ferraz-oliveira
Copy link
Collaborator

@paulo-ferraz-oliveira paulo-ferraz-oliveira commented May 20, 2021

Can't actually remember why I wanted/needed to introduce dialyzer here, but it was somehow on my TODO list.

The proposed changes only work with a yet unreleased hex_core which also caused dialyzer warnings, but is a good preview of what's to come.

Here it is:

Opening as draft for the above mentioned reasons.

Commenting on the stuff that might not be so obvious (or on which I have doubts).

rebar.config Outdated Show resolved Hide resolved
@@ -23,6 +23,14 @@
]}
]}.

{dialyzer, [
{warnings, [
error_handling,
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me know if we want unhandled_returns. unknown is usually not friendly to rebar3 plugins.

@@ -21,5 +21,5 @@ format_error({Cmd, missing_required_params}) ->
io_lib:format("Required parameters for the ~ts command have not been supplied.", [Cmd]);

format_error(Reason) ->
rebar_api:debug("Unknown error : ~ts", [Reason]),
rebar_api:debug("Unknown error : ~ps", [Reason]),
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would throw when the error is e.g. a tuple. (it was not dialyzer, but testing on an invalid repo.)

@@ -208,7 +208,7 @@ generate_all_keys(Username, Password, LocalPassword, Repo, State) ->

%% write key
WriteKeyName = api_key_name(),
WritePermissions = [#{<<"domain">> => <<"api">>}],
WritePermissions = [#{domain => api}],
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comes from hex_core's API. I'm pretty sure it works in both forms, but, as-is, it's converted later, via term_to_binary eventually (if I correctly followed the 🐰 hole).

@paulo-ferraz-oliveira
Copy link
Collaborator Author

Following #232, this has been rebased on top of master. Initial conditions, #229 (comment), still apply, though.

@paulo-ferraz-oliveira
Copy link
Collaborator Author

hexpm/hex_core#121 was merged and tagged, so I pushed a remade rebar.lock.
After jelly-beam/verl#21, CI should be all 🟢. I've been testing this locally with _checkouts.

@paulo-ferraz-oliveira
Copy link
Collaborator Author

jelly-beam/verl#21 was merged and tagged, so I pushed a remade rebar.lock. If CI's Okay that does it for my change 😄

@paulo-ferraz-oliveira paulo-ferraz-oliveira marked this pull request as ready for review May 28, 2021 13:34
@paulo-ferraz-oliveira
Copy link
Collaborator Author

I also fixed coverage stuff. It was hidden by the fact it didn't show an error.
But look at README and see it's not there.

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.

None yet

2 participants