Closed danreeves closed 6 years ago
ah shoot ๐คจ thanks for reporting!
It seems that the incoming message parser is imperfect, and it should not be failing on this. I have patchy internet at the airport right now so I'm having trouble replicating, but will write an extra test for turn.start
message parsing and try to get it behaving properly.
ok, I think I know what happened. I forgot to build the node entry file before publishing. All the same, I added some more robustness around the parser and tweaked my test message data to more accurately represent the line breaks on messages coming in from the websocket.
once the tests pass in CI I'll merge it and publish. Would love if you could then retest please :pray:
๐ข ๐ข ๐ข just shipped the fix.
Please reopen if you still run into issues. Thanks for testing out the major release so soon!
Speedy response! ๐
Looks like that fixed the issue, thanks!
node --version: v9.2.0 ms-bing-speech-service: 2.0.0
I'm probably doing something wrong, but when I try sending a Buffer the
JSON.parse
inonMessage
is exploding becausemessage.body
is just{
.Example message: