-
Notifications
You must be signed in to change notification settings - Fork 220
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
Internal coding error detected at file mlrmap_flatten_unflatten.go line 160
#1733
Comments
Hi,
I have this output [
{
"1": ".",
"2": ","
},
{
"1": "",
"2": ""
}
] |
Let me clarify a bit. The file does indeed have headers, and the first line ".", and "," are the (valid) header names. The above file was produced by a csv file (containing a lot of data) failing to convert to json, and my subsequent pruning to reduce the failure to a minimal example. Indeed, a perhaps clearer example as below fails similarly. In any case, if an error was triggered, I would expect miller to report the error rather than abort as it did.
|
Hi @irisjae the Default: if the input has y.1=7,y.2=8,y.3=9 then this unflattens to There is an auto unflatten related to You can disable it, running [
{
"header 1 .": "my info",
"header 2 ,": "more info"
}
] |
Thank you, that makes sense. Perhaps the error message should be improved. Also, if
produce
? |
The error-handling logic needs improving -- I will do so. |
Some more examples of unflatten misbehavior:
|
Inputs and outputs with #1735:
|
Thank you very much |
@irisjae @aborruso please also see (Note: these are docs for |
Save the following file as
test.csv
Now, execute
mlr --icsv --ojson cat test.csv
, which produces the errorInternal coding error detected at file mlrmap_flatten_unflatten.go line 160
.mlr --version
yieldsmlr 6.13.0
.The text was updated successfully, but these errors were encountered: