Yeah, it's a minor annoyance but doesn't seem to actually impact anything. I'm not sure which of my shaders is doing that, since it helpfully omits that information.
I think the report is on mantis, but if not it would be helpful to have there so I can remember to get to that. I think that the issue may automatically solve itself as we upgrade to newer versions of unity and/or I upgrade to a newer version of Amplify Shader Editor, so it might wind up being moot. There's also a chance that it's in part of the post-processing stack and not my issue at all, in which case the next build coming out should fix that.
Basically my choices are to wait and see if the other inevitable upcoming changes fix it, or if it's something I have to start a big game of guess-and-check with. Hopefully the former case happens.
