Web sockets error code: "Closed down 1006" reason: "Going Away"

[bergwillman]

Related to issue #1 on web socket connectivity. I have a local instance of the mac OSX version of Intu running and actively updating as indicated by continuous terminal outputs. I then run the test_topic_client.py script in a separate terminal and the following gets printed out.

TopicClient Instantiated!
Topic Client is instantiated!
Connected!
On Connected function!
Sensor Manager has been instantiated!
adding sensor id: 2ef1fbd9-af63-4191-a609-8a36b4f01be1
adding sensor id: 4d8df03d-a66d-4491-b1b2-ed4f22341bd3
SpeechGesture has started!
adding gesture id: tts
Closed down 1006 Going away

Similar to issue #1, the error "Closed down 1006 Going away" is printed following the call topic.start()

Additionally, my instance of Intu stops running after adding several proxy sensors. It terminates due to a segmentation fault with code: 11.

Here is the corresponding log output to the Intu terminal:

[05/17/17 16:16:35.589][STAT][TextExtractor] TextExtractor started
[05/17/17 16:16:35.760][STAT][SpeechToText] Connected, Global Transaction ID: 329847908, DP Transaction ID: stream-dp02-329847908
[05/17/17 16:16:38.148][STAT][TopicManager] Added connection 2
[05/17/17 16:16:38.148][STAT][TopicManager] Skipping authentication for connection 2
[05/17/17 16:16:38.148][STAT][TopicManager] Connection 2 authenticated, SelfId: 506acb2becd4a3543feca7701d2d509d
[05/17/17 16:16:38.356][STAT][SensorManager] Adding proxy sensor Camera, Id: cf52bc03-15a6-4b24-ba79-eccbfac4c98c, Override: True
[05/17/17 16:16:38.356][STAT][SensorManager] Disabling sensor Camera, Id: b3c45f6a-f22e-49fa-b57f-fd0ef6253bce
[05/17/17 16:16:38.356][STAT][ImageExtractor] Removing video sensor b3c45f6a-f22e-49fa-b57f-fd0ef6253bce
[05/17/17 16:16:38.364][STAT][ImageExtractor] Adding new video sensor cf52bc03-15a6-4b24-ba79-eccbfac4c98c
[05/17/17 16:16:38.365][STAT][SensorManager] Removing proxy sensor cf52bc03-15a6-4b24-ba79-eccbfac4c98c for origin /.
[05/17/17 16:16:38.365][STAT][ImageExtractor] Removing video sensor cf52bc03-15a6-4b24-ba79-eccbfac4c98c
[05/17/17 16:16:38.366][STAT][SensorManager] Removing proxy sensor cf52bc03-15a6-4b24-ba79-eccbfac4c98c for origin /.
[05/17/17 16:16:38.366][STAT][SensorManager] Enabling sensor Camera, Id: b3c45f6a-f22e-49fa-b57f-fd0ef6253bce
[05/17/17 16:16:38.366][STAT][ImageExtractor] Adding new video sensor b3c45f6a-f22e-49fa-b57f-fd0ef6253bce
Segmentation fault: 11

[rlyle]

Thanks, will try to reproduce this and see if can fix... I think i've got an idea what this is, since I hit a simular issue with dynamic adding/removing services.

[agrosven]

I am experiencing the same problem. This happens on both Mac OS X Yosemite and El Capitan

[rlyle]

Ok, so the python SDK works fine with the latest develop branch of Intu. We are currently working on a new release, so this will be fixed soon. I'm going to work on a method to allow you to pull the "develop" version of the SDK (which includes the latest binaries and libs) and will update this thread once that is done.

[bergwillman]

I just tried running the python test script in ubuntu 16.04 LTS and received the same error.

Could it be that the instance of Intu isn't configured to be listening to the correct port number that the python script opens up? I thought about changing that setting in the test script but then I realized that I couldn't find the corresponding .cpp file. However, I did find a WebSocketFramer.h header file in the ../../../qi/toolchains/mac-self/self/include/utils directory. Is there a corresponding body file where the listening port number is defined?