Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-06-18 | Update copyright year | Henrik Nord | |
2018-06-08 | [logger] Change base OTP domain from [beam,erlang,otp] to [otp] | Siri Hansen | |
2018-04-26 | Start using logger internally in kernel and stdlib | Siri Hansen | |
2016-03-15 | update copyright-year | Henrik Nord | |
2015-06-18 | Change license text to APLv2 | Bruce Yinhe | |
2014-02-14 | Suppress error report when child was terminated normally | bell | |
Description: Let's assume we have a supervisor_bridge as a non-permanent child of a supervisor. When the bridge terminates normally it reports by error_logger:error_report, but the supervisor does nothing. So we have tons (especially, when it's simple_one_for_one) of error messages while everything is completely ok. Let's assume we have a supervisor_bridge as a permanent child of a supervisor. When the bridge terminates, it invokes error_logger, but what for? The supervisor will invoke error_logger about this error right after that. So what is the reason for the error_logger to log for normally terminating children in this case? | |||
2011-10-07 | Add '-callback' attributes in stdlib's behaviours | Stavros Aronis | |
Replace the behaviour_info(callbacks) export in stdlib's behaviours with -callback' attributes for all the callbacks. | |||
2011-05-12 | Types and specifications have been modified and added | Hans Bolinder | |
2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |