search

alexa / avs-device-sdk

An SDK for commercial device makers to integrate Alexa directly into connected products.
https://developer.amazon.com/alexa/alexa-voice-service
Apache License 2.0
1.26k stars 602 forks source link

Very short answer from alexa on "what news" after interrupting before alexa started answering on previous question "sport updates" #1918

Open alexismailov2 opened 3 years ago

alexismailov2 commented 3 years ago

Overview

The problem is in the floating bug in playing answer after asking "what news" right after alexa starts playing answer on previous command for example "sports update". So it looks like interrupting alexa will not work correct and looks like it can be data race or wrong internal state machine.

What is the expected behavior?

Interrupting should not change usual alexa answers.

What behavior are you observing?

Alexa gives short answer on the request after it will be interrupted before alexa started answerig on previous command

Provide the steps to reproduce the issue, if applicable:

Console application

  1. run console application
  2. authorize it will not be authorized previous
  3. type 't' and press Enter
  4. start asking "sports update" and wait when alexa will start aswering
  5. right after message "Thinking" in the console type 't' and press Enter
  6. ask "whats news"
  7. Answers with one short sentence "ABC news" without long explanation

Tell us about your environment:

MacOS Big sur 11.2.3 Gstreamer portaudio http://files.portaudio.com/archives/pa_stable_v190700_20210406.tgz openssl 1.1

What version of the AVS Device SDK are you using?

  <1.23.0>

Tell us what hardware you're using:

Tell us about your OS (Type & version):

kclchan commented 3 years ago

Hi @alexismailov2, thanks for bringing this to our attention. I've opened an internal ticket to look into this. Thanks.

pavlonadolynskyi commented 3 years ago

@kclchan do you have any news?

pavlonadolynskyi commented 3 years ago

@kclchan Hi, could you pls update me on progress?

blazusiak-amazon commented 1 year ago

Hello @pavlonadolynskyi,

Are you still experiencing this on the latest version of the SDK (3.0)?