wgpu_core::validation error: unexpected varying type

[ifacodes]

Description
When I run my program, (the pipeline section from ) I get an error once it runs. it doesn't break anything, I'm just confused as to why this seems be happening.

Repro steps
following the sotrh guide with these dependencies:
[dependencies]
anyhow = "1.0.40"
image = "0.23.14"
winit = "0.24"
wgpu = "0.8.1"
env_logger = "0.7"
futures = "0.3"
cgmath = "0.18"

[build-dependencies]
shaderc = "0.7"
anyhow = "1.0.40"
fs_extra = "1.1"
glob = "0.3"

Expected vs observed behavior
for this error not to happen.

Extra materials

I think?? It has something to do with the SPIR_V vec4 formats?

Platform
Windows 10, wgpu 0.8.1

[kvark]

You are providing a SPIR-V shader built from GLSL. It contains things like gl_ClipDistance and gl_CullDistance that aren't a part of WebGPU, so we have to work around them. The released wgpu-0.8.1 doesn't know how to work around the gl_CullDistance thing at least, so there is your error.
Try changing the #version in GLSL to 440 instead of 450 or 460 that you are using.

[ifacodes]

that... didn't help unfortunately I'm facing the same error. any other solution?

[ifacodes]

these are my only two shaders

[kvark]

Ok, sorry, I should have read it more carefully. You are saying everything works, just wondering why the error is printed.
The answer is - WebGPU has no such thing as "gl_ClipDistance" or "gl_CullDistance", and they are arrays, which WebGPU doesn't support for inputs/outputs of the shader. So the validation yells at you for this. In the future we may be handling this better.

[HalfVoxel]

I also got this issue and spent a fair amount of time trying to debug my shader to see what the issue was, before finding this post.
This only became an issue when I upgraded to the latest wgpu, earlier versions seemed to handle it without any issues.

[ifsheldon]

I have the same issue when learning wgpu with this tutorial. Maybe you could just be more specific in the error message as a quick fix

[kvark]

Error messages coming from Naga are indeed not very actionable right now, this is a general problem we are aware of but hasn't solved yet.

[cwfitzgerald]

See #2168 for more info