enricobuehler
6092f80df2
ci / bun-nix (pull_request) Successful in 28s
ci / docs-drift (pull_request) Successful in 35s
ci / web (pull_request) Successful in 1m43s
ci / docs-site (pull_request) Successful in 1m42s
ci / rust-arm64 (pull_request) Successful in 1m48s
apple / swift (pull_request) Successful in 2m19s
apple / distribute (pull_request) Skipped
apple / screenshots (pull_request) Skipped
android / android (pull_request) Successful in 7m14s
ci / rust (pull_request) Failing after 7m0s
windows-client / client (arm64, --no-default-features, aarch64-pc-windows-msvc, C:\t-a64) (pull_request) Successful in 6m55s
windows-client / client (x64, , x86_64-pc-windows-msvc, C:\t) (pull_request) Failing after 8m25s
PUNKTFUNK_RENDER_NODE had three independent readers disagreeing on trim and empty-string handling (pf-gpu: no trim; pyrowave: trim+filter; the remote worker handshake: raw .ok(), so an empty or padded value crossed the process boundary verbatim). pf_gpu::render_node_env() is now the one parse; linux_render_node layers the console's manual GPU preference on top, and the PyroWave sites keep reading the env-only form deliberately — their device-selection oracle rules forbid the preference layer.