Correctly print cmdline errors with braces #3880
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
While I was testing some edge case
install
stanzas for @JonnyOThan, this metadata:gave me this error:
Cause
The root cause is that my .ckan file was formatted wrong; the
install
property has to be an array, but mine was an object, so the attempt to deserialize failed.However, the error message about that was not printed because there are places in CmdLine where a message string from an exception thrown by core code or third party libraries is passed as the first parameter of
IUser.RaiseError
, which always interprets that parameter as a format string (see #2111). If such a string contains{
and}
(as is particularly likely for JSON deserialization problems), these will be interpreted as parameter interpolation tokens and the string formatting will fail.Changes
{0}
, to prevent the message from being interpreted as a format string. The original root cause error is printed: