generated from duckdb/extension-template
-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
On a couple of linuxes (Ubuntu, Mint) running duckdb v1.4.2 with shellfs, I see some issues which I didn't see a couple of months ago. Core dump or "empty result".
For example when doing this:
-- Loading resources from /home/ubuntu/.duckdbrc
DuckDB v1.4.2 (Andium) 68d7555f68
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D load shellfs;
D set ignore_sigpipe = true;
D from read_text('cat /etc/issue |');
terminate called after throwing an instance of 'duckdb::IOException'
what(): {"exception_type":"IO","exception_message":"Pipe process exited abnormally code=141: cat /etc/issue |"}
Aborted (core dumped)
Also from read_text('cat /etc/issue {allowed_exit_codes=141}|') returns empty content, unlike when using the ".sh cat /etc/issue" which can redirect to a file and reading this with read_text inside the CLI succeeds.
Metadata
Metadata
Assignees
Labels
No labels