Brent Williams

Thanks @ilikerobots, I can confirm changing `selected` to true got rid of the error. Leaving issue open for you to resolve when you see fit.

Added to stackflow as well (https://stackoverflow.com/questions/60332365/net-core-3-1-dotnet-svcutil-generated-wcf-proxy-and-even-a-custom-channel-a), critical blocker for us.

Hi @StephenBonikowsky thanks for reply. Unfortunately I can't send full WSDL without private channel + NDA, however I have stripped it down to the method in question. dotnet-svcutil runs produces...

Great anything I can do to help let me know. True the server is not WCF, was written in C/gSOAP.

FYI this problem was duped & a workaround found _for the stripped-down-wsdl only_ on stackoverflow (https://stackoverflow.com/questions/60332365/dotnet-svcutil-generated-wcf-proxy-and-even-a-custom-channel-are-returning-n). A solution to generate a usable proxy directly from dotnet-svcutil for the full wsdl...

@StephenBonikowsky great you have a repro. The stackoverflow fix works for single-method WSDL, but for 2+ methods I couldn't find a combination of namespace values to get the proxy built...

> e-parse shader via `naga` lib to handle error Just a comment RE: @lebedec, naga::front::wgsl.parse_str() will trap some errors e.g. "uv.u" instead of "uv.x" but wgpu::device.create_shader_module() will catch a further...

Same issue as @songlinshu. Not sure I'd call it a bug but definitely either an upgrade to latest polars or almost as good a line or two on how to...

@MoeNeuron idle-vue just wraps idle-js, you can use idle-js directly in Vue 3 without any issues.