Phil Rzewski

Extra output when yielding literals as input data

1

## tl;dr I can't explain why the first line of output is repeated twice here. ``` $ zq -z ' yield [{id:1},{id:2}] | over this | left join ( yield...

## tl;dr As a user, the field name `cast` seems unexpected here. ``` $ echo '{x:1, y:2}' | zq 'cut x,float64(y)' - {x:1,cast:2.} ``` ## Details Repro is with Zed...

Conditional grep in record index expression seems buggy

1

## tl;dr The output from the following seems incorrect compared to when we compute each part separately and combine. ``` this[grep(one*, x) ? "one" : "two"]:=x ``` ## Details Repro...

Intentional early exit

2

## tl;dr A user may want to craft a pipeline that intentionally stops processing the input stream when a particular condition is met. ## Details At the time this issue...

## tl;dr This error message speaks of an expression/integer, but it actually takes a compile-time constant expression that evaluates to a positive integer, which is more limiting. ``` $ zq...

## tl;dr As a user, this result seems incorrect to me. ``` $ echo '0.99 (float32)' | zq -Z 'yield this > 0.99' - true ``` ## Details Repro is...

## tl;dr This gives the one expected line of output, but then hangs and does not exit. ``` $ echo '3 1 4 1 5 9 2 6 5 3...

Zed CLI tools won't output ZNG to terminal even if explicitly requested

1

## tl;dr The following still produces ZSON output despite the `-f zng`. ``` $ echo '{ts:2024-08-14T19:12:51Z}' | zq -f zng - {ts:2024-08-14T19:12:51Z} ``` ## Details Repro is with Zed commit...

## tl;dr This hangs for me: ``` $ for n in $(seq 1 701); do echo "{ts:$n}"; done | zq -z 'fork (=>pass =>pass) | merge this' - {ts:1} {ts:1}...

CI recently had a [test failure](https://github.com/brimdata/zed/actions/runs/10865226064/job/30151453342) in [lake/journal/journal_test.go](https://github.com/brimdata/zed/blob/main/lake/journal/journal_test.go). Upon checking with @nwt I was informed: > It's a bug in the test, not the implementation, and so it isn’t user-facing....