WASM basline compiler (winch) panics on MacOS

[ignatz]

[2026-01-02T16:00:18.955522Z INFO  trailbase_wasm_runtime_host::functions] Loaded component "traildepot/wasm/component.wasm" in: 622.456ms.

thread 'main' (25356) panicked at /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wasmtime-wasi-40.0.0/src/runtime.rs:108:15:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
stack backtrace:
   0:        0x1030e4388 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h2808c764b780ef77
   1:        0x102816e40 - core::fmt::write::h164e2e78980a3344
   2:        0x1030e3e14 - std::io::Write::write_fmt::hc5b2a4d160c11c86
   3:        0x1030e4248 - std::sys::backtrace::BacktraceLock::print::h765d16e49e83c7b3
   4:        0x1030e3abc - std::panicking::panic_with_hook::h93c775fc227522dd
   5:        0x1031011e8 - std::panicking::panic_handler::{{closure}}::h8561e58c9391724a
   6:        0x103101180 - std::sys::backtrace::__rust_end_short_backtrace::h55629ed76aaa9d26
   7:        0x103101174 - __rustc[d9b87f19e823c0ef]::rust_begin_unwind
   8:        0x10420a7e4 - core::panicking::panic_fmt::hfe9cfd57c06d80d9
   9:        0x103de9ffc - wasmtime_wasi::p2::host::io::<impl wasmtime_wasi::p2::bindings::sync::generated::wasi::io::streams::HostOutputStream for wasmtime::runtime::component::resource_table::ResourceTable>::blocking_write_and_flush::hb04893a5988d4cb8
  10:        0x1039409d8 - wasmtime::runtime::component::func::host::HostFunc::entrypoint::{{closure}}::{{closure}}::h361b6f8cd98b66ab
  11:        0x10393f664 - wasmtime::runtime::component::func::host::HostFunc::entrypoint::h3df86ac3652bd8ac
  12:        0x10a06cdec - <unknown>
dist/index.js  21.72 kB │ gzip: 6.04 kB
✓ built in 74ms
file:///Users/sebastian/projects/trailbase/node_modules/.pnpm/nano-spawn@2.0.0/node_modules/nano-spawn/source/result.js:40
throw new SubprocessError(`Command failed with exit code ${exitCode}: ${command}`);
     ^

SubprocessError: Command failed with exit code 101: trail '--data-dir=traildepot' run --dev '-a=localhost:4000'
    at checkFailure (file:///Users/sebastian/projects/trailbase/node_modules/.pnpm/nano-spawn@2.0.0/node_modules/nano-spawn/source/result.js:40:9)
    at getResult (file:///Users/sebastian/projects/trailbase/node_modules/.pnpm/nano-spawn@2.0.0/node_modules/nano-spawn/source/result.js:17:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {
  exitCode: 101,
  stdout: '',
  stderr: '',
  output: '',
  command: "trail '--data-dir=traildepot' run --dev '-a=localhost:4000'",
  durationMs: 660.721916
}

Somehow, tokio is being nested differently 🤷‍♀️ . Don't understand it yet but let's disable winch on MacOS for now, which is not ideal for devex but better than crashing.