On 10.06.2016 19:08, John Mazzitelli wrote:
I'm having a hard time getting its embedded agent to create and
maintain its websocket - many times it gets closed with an odd reason code of 1006 (no
other explanation). In addition, sometimes (a lot of times) when I try to connect to it
via websockets using a third-party tool, I'm getting the same behavior (code 1006).
Are you able to reproduce it with the nest? If so, it should be possible
to identify the commit that introduced this by using "git bisect". I can
help you with that.
- Juca.