From 73fe87fdb5ad82a750c93f6c7efd8489e126dfca Mon Sep 17 00:00:00 2001 From: Ruben Fiszel Date: Thu, 6 Aug 2026 17:30:24 +0000 Subject: [PATCH] fix: explain duckdb failures caused by job isolation Co-Authored-By: Claude Opus 5 (1M context) --- backend/ee-repo-ref.txt | 2 +- backend/windmill-worker/src/duckdb_executor.rs | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/backend/ee-repo-ref.txt b/backend/ee-repo-ref.txt index 91d0c51cf7..1557233756 100644 --- a/backend/ee-repo-ref.txt +++ b/backend/ee-repo-ref.txt @@ -1 +1 @@ -181fa0c206d7f84a289b4396a7f7764bc815d284 +9b6e7cac8d757283ef5455d16749810dfa4a9330 diff --git a/backend/windmill-worker/src/duckdb_executor.rs b/backend/windmill-worker/src/duckdb_executor.rs index e91a1957c6..91af3e763a 100644 --- a/backend/windmill-worker/src/duckdb_executor.rs +++ b/backend/windmill-worker/src/duckdb_executor.rs @@ -1641,6 +1641,8 @@ pub async fn do_duckdb( let (result, column_order) = match result { Ok(r) => r, Err(e) => { + #[cfg(feature = "private")] + let e = crate::duckdb_isolation_ee::explain_error(e); if let Some((_, meta)) = &materialize { record_mat( conn,