Closed eproxus closed 1 week ago
Well, yes it is annoying. You can of course filter them out if you really want progress reporting on in the first place (I view it as legacy debug feature). But for a long term solution I think that progress reporting should only be done for static parts of application supervisor trees.
Describe the bug When progress logging is enabled and TLS is used, there is a supervisor
tls_dyn_connection_sup
started that logs all arguments used to started it.When passing a custom certificate list to TLS start options, these are included as-is in the
cacerts
option to this supervisor which results in megabytes and tens of thousands of lines of logs every time this process is started (often resulting in making it impossible to see any lines before this in the terminal since most terminals have a default line limit well below this).To Reproduce Start an SSL connection with options like
[{cacerts, public_key:cacerts_get()}]
(or use e.g. tls_certificate_check).Expected behavior Logs are useful and readable.
Affected versions 27.0.1 (and earlier)
Additional context
Example: