-
Notifications
You must be signed in to change notification settings - Fork 456
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
lager_truncation_size does not work #211
Comments
It works if I use it like this:
With a file like this: -module(test).
-export([start/0]).
-compile([{parse_transform, lager_transform}, {lager_truncation_size, 100}]).
start() ->
lager:info("~p", [string:copies("hello wrld", 20)]). But note that the -compile option inside the module does not work (don't ask me why). |
I can't find |
It is created via a parse transform. |
Thank you, really it works by lager:info, but truncation doesn't work if you call error_logger:info_msg. Message truncated by DEFAULT_TRUNCATION
can you fix it? |
Right, those messages are covered by a different truncation limit, which is not (currently) configurable. |
The transform could check the attributes in the AST for lager_truncation_size if it can't find it in the options. This would allow lager_truncation_size to be specified in the -compile attribute in the module. It is confusing that it doesn't work, though that is nothing to do with lager :) |
Dup of #162 |
option
{lager_truncation_size, 1024}
does not work on current master
Data was truncated on default (?DEFAULT_TRUNCATION) size
The text was updated successfully, but these errors were encountered: