[GROOVY-11270] Don't truncate argument types in MissingMethodException

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.17
• Fix Version/s: 5.0.0-alpha-7, 4.0.20, 3.0.22
• Component/s: groovy-runtime
• Assignee: Eric Milles
• Reporter: Christopher Smith
• Created: 05/Jan/24 20:51
• Updated: 24/Mar/24 23:12
• Resolved: 14/Mar/24 00:13

Description

The MissingMethodException#getMessage():63 builder truncates the string indicating the types of the supplied (mismatching) arguments at 60 characters, which may not be enough to contain a single FQCN. I have spent a good deal of time debugging an error in which heap pollution and updated enforcement of type checking causes a List that is erroneously passed to a closure expecting a Set used to work (only basic collection methods are called) but now fails.

The error message truncates the type of the runtime arguments, which would have instantly revealed the problem (List instead of Set). I don't see a good reason why this important information should be truncated, at least at anything short of a very high limit (4k or so). I request replacement of the 60-character limit with -1 or at least 4096.