-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing quotes gives misleading error message #413
Comments
Thanks for reporting! I think it's a bug about the lexer when scanning integer type values |
I wonder if it's specific to integer type values. I got a similar error when quotes were missing from this line:
I'm not sure if the error message was the same. At some point while I was working on this, the error message was But definitely in both cases, the solution was to add ""s around the value. |
It's not specific to integer types. I had:
and got the "keys cannot contain new line" error. This was corrected by correcting my config:
|
Looks like that's still not great in v2: https://play.golang.org/p/9xauDfRSQI7
cc @vincentserpoul, on the topic of providing more meaningful errors. |
Good insight on #858: maybe we should consider passing the type of the target to provide a more accurate error. |
Describe the bug
The error message for missing quotes is misleading.
To Reproduce
timeout_broadcast_tx_commit = 20s
in a .toml fileERROR: While parsing config: (136, 33): parsing error: keys cannot contain new lines
Expected behavior
ERROR: While parsing config: (136, 33): parsing error: value requires quotes
or some suchVersions
Additional context
see also cosmos/cosmos-sdk#5165
The text was updated successfully, but these errors were encountered: