Sam Sharp

@JamesMc86 I have also started seeing the same issue recently - it seems to be quite intermittent but has started to cause quite a few of our builds to fail...

> Thanks Sam. I'll move this up my priorities as it should be simple enough to supress. Great, thanks James - if you want me to try/test an updated build...

You need to install HACS and add a custom repository there.

Can you share an example/screenshot of your code that replicates the issue? Error 56 is a timeout error which means that a full/complete packet was not received, or no packet...

Hi Lucas, The [WebSockets specification](https://tools.ietf.org/html/rfc6455#section-5.5.1) states: > The Close frame MAY contain a body (the "Application data" portion of the frame) that indicates a reason for closing The closing body...

Yes, that's OK - I will leave the issue open and have no issue with implementing it at some stage but if the Python side is generating an exception/error then...

Hi @christandlg - thanks for raising the issue. There are a couple of things this could be: - The 'read' is timing out and returning the partial data/message (the timeout...

Proposed PURL types: **nipkg** nipkg for NI Package format packages namespace is the maintainer from the package attributes (optional) name is the package name from the package attributes version is...

@iamwillbar Thanks - it's taken a while to get around to it but I have submitted a PR to add these formats.

Hi - I believe the website might have deprecated non-secure (ws://) WebSockets connections and now only allow secure connections (wss://) Try changing the ws:// to wss:// and see if that...