Don't log full message on serialization errors?

[stwirth]

We recently had a bug in a python script which made the serialization of a sensor_msgs/Image fail. The result was that the full image was logged to rosout, making the logs grow by multiple megabytes per second.

  File "/[...]/python3.8/site-packages/genpy/message.py", line 385, in _check_types
    raise SerializationError(str(exc))
genpy.message.SerializationError: <class 'TypeError'>: 'string argument expected, got 'bytes'' when writing 'header: 
  seq: 234328
  stamp: 
    secs: 1670536260
    nsecs: 942930698
  frame_id: "camera_down_infra1_frame"
height: 240
width: 320
encoding: "mono8"
is_bigendian: 0
step: 320
data: [4, 3, 3, 4, 3, 4, 3, 4, 4, 4, 3, 3, 4, 3, 3, 3, 3, 4, 3, 3, 3, 3, 3, 4, 3, 3, 4, 3, 3, 3, 3, 4, 3, 4, 3, 4, 3, 3, 3, 3, 3, 3, 4, 4, 3, 3, 4, 3, 4, 3, 3, 3, 3, 3, 4, 4, 3, 3, 4, 3, 3, 3, 4, 4, 3, 3, 4, 4, 3, 4, 3, 3, 3, 3, 3, 3, 4, 3, 4, 3, 3, 3, 3, 3, 3, 3, 4, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 4, 3, 3, 3, 4, 4, 4, 4, 4, ...

This is bad for log management and also bad for SSDs.

I'd like to have the option to not log full messages to rosout on serialization errors.
Alternatively, the logging module in rospy could be changed to be able to enforce a maximum log message size.
What do you think?