Alexey Milovidov 1e169c43ee Resolve execute_direct commands in dynamic UDF workdirs ...

Resolve `execute_direct` commands for driver-generated executable UDFs relative to the function's UUID working directory from the `.workdir` sidecar instead of `user_scripts_path`.

This lets the C example drivers emit relative commands such as `user_func` and `docker_fifo_runner.sh`, while regular executable UDF configs continue to use `user_scripts_path`.

Tests:
- `python3 -m py_compile programs/server/user_defined_executable_function_drivers/c_driver_common.py`
- `ninja -C build programs/clickhouse`
- `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:13:30 +02:00

..

c_driver_common.py

Resolve execute_direct commands in dynamic UDF workdirs

2026-05-17 01:13:30 +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