Another thing that was mentioned is either putting a cap on error summary logs - so skipping them if they are too large and/or limiting the size of the line we store in the tables. We do that now for the raw summary/live backing logs (in `post_log_artifacts` and I think also in the parser itself) but not for the error summary logs.
Bug 1679162 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Another thing that was mentioned is either putting a cap on error summary logs - so skipping them if they are too large and/or limiting the size of the line we store in the tables. We do that now for the raw summary/live backing logs (in `post_log_artifacts` and I think also in the parser itself) but not for the error summary logs. Edit: but otherwise, that summary sounds good :)
Another thing that was mentioned is either putting a cap on error summary logs - so skipping them if they are too large and/or limiting the size of the line we store in the tables. We do that now for the raw summary/live backing logs (in `post_log_artifacts` and I think also in the parser itself) but not for the error summary logs. Edit: but otherwise, that proposal sounds good :)