Hey,

so I run into this a few times while fixing pyodide issues with the new release (and I am currently running into some race conditions with raising - so this was not making it easier). Turns out the problem is with windows.

You emit this user warning UserWarning: fpl highlight: anchor '@fragment\nfn fs_main' not found in image.wgsl FS entry WGSL. Highlighting disabled for this graphic type. This is likely caused by a pygfx version change, update the anchor string. But the assembly still fails leading to a validation error.

I had this happen with the example imgui_colorbar.py but there is likely others that also make use of your shader patching.

What happens is that get_code() returns different newlines on windows. The classic \r\n which of course doesn't match the expected \n for your anchors. To me this is actually something that should be fixed in pygfx, but as a quick workaround you can just do .replace("\r\n", "\n").

Maybe this doesn't happen to wheels built on CI, but I am on editable builds of the whole stack (wgpu-py, pygfx, fastplotlib; all on main)?

I think this is part of the whole custom shader maintenance discussion.