Giorgi / DuckDB.NET / 37241759916

93%

push

github

Make the late streaming error tests work on DuckDB 2.0

Four tests need a streaming query to fail only after some rows were
read. With default settings that no longer happens on DuckDB 2.0: it
buffers past the failing row, discards the buffered rows when the error
occurs, and reports the error from ExecuteReader, before any row is
returned. On DuckDB 1.5 the same tests sometimes failed with
OperationCanceledException, because an error on a worker thread can be
reported as an interrupt.

The tests now use a private in-memory connection with threads=1 and a
100KB streaming buffer. One thread produces the chunks in order and can
get only a few chunks ahead of the reader, so the rows before the
failing one are read first on both versions. One thread alone was not
enough on 2.0. streaming_buffer_size is a per-connection setting, so it
is applied with SET; the connection string rejects it.

Verified on DuckDB 1.5.6 and on v2.0.0-alpha44255: the four tests pass
6 runs out of 6 on each.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CzLKjBGAwccxYB6ny5bpmY

1611 of 1905 branches covered (84.57%)

Branch coverage included in aggregate %.

3244 of 3569 relevant lines covered (90.89%)

420558.47 hits per line