#Stdout/stderr mangled in sidecar

7 messages · Page 1 of 1 (latest)

white geyser
#

Seems like v2 tauri keeps cutting off stderr and stdout too early.

Only happening on windows, tried with ffprobe binary, using in command line returns correct stdout consistently, while sidecar.execute in tauri cuts off the response randomly

[✔] Environment

OS: Windows 10.0.22621 X64
✔ WebView2: 118.0.2088.76
✔ MSVC: Visual Studio Community 2022
✔ rustc: 1.73.0 (cc66ad468 2023-10-03)
✔ Cargo: 1.73.0 (9c4383fb5 2023-08-26)
✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
node: 18.18.2
pnpm: 8.10.0
npm: 9.8.1

[-] Packages

tauri [RUST]: 2.0.0-alpha.17
tauri-build [RUST]: 2.0.0-alpha.11
wry [RUST]: 0.34.2
tao [RUST]: 0.23.0
@tauri-apps/api [NPM]: 2.0.0-alpha.9
@tauri-apps/cli [NPM]: 2.0.0-alpha.16

[-] App

build-type: bundle
CSP: unset
distDir: ../dist
devPath: http://localhost:8080/
framework: React
bundler: Vite

white geyser
#

switched from using sidecar to invoke, and calling binary from invoke handler

#

works perfectly, and way faster

wary hill
#

😮

#

nice

rugged grove
#

@white geyser how have you called a binary from invoke handler? Are you just calling the same sidecar binary just from rust instead, or are you manually using std::process::Command or something?

white geyser