Note the empty record shown in on:{}.
$ super -version &&
echo '{"a":"b"}' | super -s -i json -dynamic -c "values foo" -
Version: v0.3.0-378-g2338849bb
error({message:"no such field foo",on:{}})
Details
Repro is with super commit 2338849.
By comparison, with -i sup, the on shows the input record.
$ echo '{"a":"b"}' | super -s -i sup -dynamic -c "values foo" -
error({message:"no such field foo",on:{a:"b"}})
I had Claude look deeper and captured its findings in a Gist. The tl;dr seems to be that it's related to projection pushdown in the JSON reader, and specifically that JSON didn't get the same string-error treatment vcache got in #7290. I also had it scope its guess on what it might take to fix and it estimated it was a "moderate" amount of effort, so I didn't burn tokens telling it to actually attempt a draft fix.
Note the empty record shown in
on:{}.Details
Repro is with super commit 2338849.
By comparison, with
-i sup, theonshows the input record.I had Claude look deeper and captured its findings in a Gist. The tl;dr seems to be that it's related to projection pushdown in the JSON reader, and specifically that JSON didn't get the same string-error treatment vcache got in #7290. I also had it scope its guess on what it might take to fix and it estimated it was a "moderate" amount of effort, so I didn't burn tokens telling it to actually attempt a draft fix.