Alexey Milovidov 9fb7dbabd4 Run DockerC FIFO runner through shell exec ...

Use `<execute_direct>0</execute_direct>` for the generated `DockerC` FIFO
runner command and prefix the command with shell `exec`. This avoids the
`user_scripts_path` validation that applies to direct executable commands,
because the runner lives in the dynamic UDF work directory, not in
`user_scripts`.

PR: https://github.com/ClickHouse/ClickHouse/pull/105131

Tests:
- `python3 -m py_compile programs/server/user_defined_executable_function_drivers/c_driver_common.py`
- `CLICKHOUSE_C_DRIVER_COMPILE_LOCAL=1 CLICKHOUSE_C_DRIVER_SKIP_DOCKER_CONTAINER=1 docker_c_create.sh --return UInt64 --args 'x UInt64, y UInt64'`
- `CLICKHOUSE_BINARY=./build/programs/clickhouse tests/queries/0_stateless/04241_executable_udf_driver.sh`
- `CLICKHOUSE_BINARY=./build/programs/clickhouse tests/queries/0_stateless/04242_executable_udf_driver_errors.sh`

2026-05-17 01:05:45 +02:00

..

c_driver_common.py

Run DockerC FIFO runner through shell exec

2026-05-17 01:05:45 +02:00

docker_c_create.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

docker_c_drop.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

gvisor_c_create.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

gvisor_c_drop.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

unsafe_c_create.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

unsafe_c_drop.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00