kvid

@WillNotAccept - Thank you for reporting this error message, but please always provide all information about your set of versions as described in [contributing guidelines](https://github.com/wireviz/WireViz/blob/master/docs/CONTRIBUTING.md) and how you installed WireViz...

@WillNotAccept wrote: > I'll take a look. I wasn't expecting a programming task to create a wire harness. It took me a while to realize that's what you were suggesting...

I just tried processing the YAML input provided above with WireViz from my [fix355](https://github.com/wireviz/WireViz/tree/fix355) branch without errors. As expected, I got the following warning and the diagram output shown below:...

I suggest you create a separate issue for "the referencing by pin name" you still experience, and please include a simple example YAML input that triggers the problem, and provide...

@KlopDesign - Thank's for trying out our new release, and reporting your problem here! Can you please provide the information specified in [CONTRIBUTING.md](https://github.com/wireviz/WireViz/blob/master/docs/CONTRIBUTING.md) to enable others to re-create your error...

It seems you have found a bug that isn't triggered by the tests we have done. How do you execute WireViz? Please include a copy of the command line including...

I'm not able to reproduce the reported OSError here, but I notice my Python version is older than what @alecraymond uses, but newer than what @KlopDesign uses. My Graphviz versions...

I have updated my log above to also include the extra commands @alecraymond just used, in case it might help to compare...

@JarrettR - Thank's a lot for finding the errno value of the raised OSError and suggesting the fix! I've not yet been able to reproduce this error myself. Since you...

The relevant fixes are merged into the `release/v0.4.1-rc` branch of PR #365 that is not yet released, but also describes how you can install the collection of fixes before the...