-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove dependency on hut #267
Conversation
Thank you so much. 💛 |
The OTP log macros expect either a text string or a map with an error report. |
Oh, but why do you need a new header file? I think it might be better to just use OTP |
The kernel's ?LOG_* macros prefer log reports as opposed to formatted log messages, so, to use them directly would require to convert all calls to pass log reports (i.e. a hash table of key/value pairs). This is doable but not a backward-compatible change for logging in this project. |
Regarding the failing CI run - in OTP 24 the erlang:get_stacktrace/0 was removed, and the |
|
For some reason when running in OTP 24 this was causing some crash errors in the logger. Maybe it was something related to my environment. I'll double check. |
The issue was related to my local environment. It seems to be good now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks good, but not sure about Ranch upgrade
rebar.config
Outdated
@@ -26,8 +26,7 @@ | |||
{smtp_rfc822_parse, return_error, 2} | |||
]}. | |||
|
|||
{deps, [{ranch, ">= 1.7.0"}, | |||
{hut, "1.3.0"}]}. | |||
{deps, [{ranch, "2.0.0"}]}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This version change seems unrelated. Is it necessary?
I think we have some code to support both 1.x and 2.x. So, if you really want to drop 1.x support, it's better to do as a separate PR.
Is this really necessary to include
|
I honestly don't have an opinion on whether include it or not. But I think it might be nice to at least have a fixed version of rebar3 in CI (by, eg, downloading it not from https://s3.amazonaws.com/rebar3/rebar3 but from, say, github releases: https://github.com/erlang/rebar3/releases/download/3.16.1/rebar3; not sure which exact version would work here though) |
The newest rebar3 only works with the last three OTP versions (it doesn't run anymore on OTP20). With Zotonic we tried to download a fixed version from GH, but we ran into build issues where our downloads were failing. We reverted back to using the newest rebar3 version. |
@mworrell, wouldn't it make sense though to make the version-specific |
Is there anything I (as noob) can help to get this pull request ready? |
#273 has been merged, so this can now be rebased on top of master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, may you, please, revert your changes in rebar3
file? We already updated it in #273
Remove extra brackets Revert ranch version change Revert rebar3
Guess this line should be removed as well: Line 47 in d012840
|
Also please consider adding the smth like
so later some special treatment can be done for the logs originating from from the gen_smtp, say: {handler, default, logger_std_h,
#{
level => debug,
filters => [{stop_gen_smtp, {fun logger_filters:domain/2, {stop, sub, [gen_smtp]}}}],
... but I won't insist if you have no time for that. |
May I kindly ask if there is a chance to get this into the next release. |
Created a new PR #309 that does more or less the same |
Merged #309 |
Closing, as #309 has the same effect of removing hut. |
Removed logging dependency on
hut
.