Actions
Defect #21226
closedSome log messages are missing the "MailHandler" prefix
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
For email scraping we set RAILS_ENV
to development
to increase logging details. This allows us to diagnose the various scraping issues we encounter and work around them.
Other scraping failures from what I can tell include the MailHandler:
prefix before the error message. Either by intention, or a nice side effect, having that prefix in the log file allows for parsing of the log file by reporting scripts.
Today I encountered a scraping issue due to the contents of an email exceeding the limits of the description column. Here is an example entry in the log from that failed scraping attempt:
An unexpected error occurred when receiving email: Mysql2::Error: Data too long for column 'description' at row 1: INSERT INTO `issues` (`project_id`, `author_id`, `priority_id`, `tracker_$ Message 30130 can not be processed
This entry is missing the MailHandler:
prefix that I am accustomed to seeing. Is this by design or is it really missing the prefix?
Actions