You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error message contain sanitized ANSI escape sequences, which make it unreadable.
ERROR bevy_render::render_resource::pipeline_cache: failed to process shader error:
\x1b[0m\x1b[1m\x1b[38;5;9merror\x1b[0m\x1b[1m: failed to build a valid final module: Entry point fragment at Fragment is invalid\x1b[0m
\x1b[0m\x1b[36m┌─\x1b[0m shaders/custom_material.wgsl:13:12
\x1b[0m\x1b[36m│\x1b[0m
\x1b[0m\x1b[36m13\x1b[0m \x1b[0m\x1b[36m│\x1b[0m return \x1b[0m\x1b[31m(material_color * textureSample(material_color_texture, material_color_sampler, mesh.uv) * "shaders/custom_material_import.wgsl"::COLOR_MULTIPLIER).rgb\x1b[0m;
\x1b[0m\x1b[36m│\x1b[0m \x1b[0m\x1b[31m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\x1b[0m \x1b[0m\x1b[31mnaga::ir::Expression [10]\x1b[0m
\x1b[0m\x1b[36m│\x1b[0m
\x1b[0m\x1b[36m=\x1b[0m The `return` expression Some([10]) does not match the declared return type Some([0])
Additional information
This is probably caused by tokio-rs/tracing@4c52ca5 (tracing-subscriber 0.3.20). It seems like users can no longer output logs with ANSI escape sequences.
This is a tracing-subscriber 0.3.20 change, ansi codes are no longer allowed in log content regardless of with_ansi configuration.
This log is being colorized by naga-oil and can be worked-around user side by setting NO_COLOR.
NO_COLOR=true cargo run
ERROR bevy_render::render_resource::pipeline_cache: failed to process shader error:
error: no definition in scope for identifier: `psbr_input`
┌─ shaders/terrain.wgsl:101:15
│
101 │ let uv = (psbr_input.material.uv_transform * vec3(in.uv, 1.)).xy;
│ ^^^^^^^^^^ unknown identifier
│
= no definition in scope for identifier: `psbr_input`
Activity
ChristopherBiscardi commentedon Sep 22, 2025
This is a tracing-subscriber 0.3.20 change, ansi codes are no longer allowed in log content regardless of
with_ansiconfiguration.This log is being colorized by naga-oil and can be worked-around user side by setting
NO_COLOR.alice-i-cecile commentedon Sep 22, 2025
Should we just pin our tracing-subscriber version for now?
EDIT: @james7132 replies: " Given it's a security vulnerability, I would rather us not do so."
tychedelia commentedon Sep 23, 2025
bevyengine/naga_oil#129
Temporarily disable color on logs due to tracing regression (#129)
alice-i-cecile commentedon Sep 26, 2025
Fixed (well, mitigated) by the new naga_oil release.
Stop rendering escaped ANSI sequences in wesl errors (bevyengine#25464)
Stop rendering escaped ANSI sequences in wesl errors (bevyengine#25464)