Description
Describe the bug
Is anyone having trouble making lex v2 runtime work on debian 12? I have previously been running aws-sdk-cpp tag 1.8.129 on debian 11 and it worked fine. Now on debian 12 I have update to the latest (1.11.217) and things are not working at all. I am connection ok and sending audio, but not getting any responses back other than a heartbeat. No transcripts and no intents.
I also had trouble with a similar upgrade with aws_transcribe, and ended up having to switch to using the websocket api instead of the sdk. Is there a websocket api for lex?
Expected Behavior
I expected to receive messages from lex v2 - intents and transcriptions.
Current Behavior
Here is a trace file showing what I received.
aws_sdk_2023-12-05-01.log
Reproduction Steps
debian 12 and using
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.11.217
Compiler and Version used
gcc (Debian 12.2.0-14) 12.2.0
Operating System and version
Debian 12
Activity
davehorton commentedon Dec 5, 2023
I can add more details, and more strange results. Today I tested with a longer call -- I connected to lex (the sample flight book bot) and said "I'd like to book a flight". For about a minute no responses other than heartbeats, then a full minute or more later I get a transcript (i'd like to book a flight), followed by a message indicating an internal error, see below
In case its possible to retrieve any logs from the server side the conversation url was
Again, this code worked fine on earlier versions of the sdk and debian.
davehorton commentedon Dec 5, 2023
Here is another example. I placed a call, immediately said "I'd like to book a flight" and after about one minute and 20 seconds later I got the transcript followed by the intent. What could be accounting for this delay?
[-]Lex v2 not working on debian 12[/-][+]Lex v2 not working (i.e. incredibly slow) on debian 12[/+]davehorton commentedon Dec 5, 2023
Note: developing to lex v2 is hampered by the fact I have not found any examples in this repo or elsewhere. If there is a working example I could test with (similar to the getTranscript example for aws transcribe) this would be very helpful for developers
jmklix commentedon Dec 6, 2023
I'm working on creating a sample using lexv2. I will post it here when I have that finished
davehorton commentedon Dec 6, 2023
great, many thanks! In the meantime let me know if I can do anything to provide additional information
davehorton commentedon Dec 11, 2023
just checking in....anything new on this?
davehorton commentedon Dec 15, 2023
anything new on this? I'm blocked by this so if I can do anything to gather information please let me know
davehorton commentedon Jan 17, 2024
HERE IS A SAMPLE PROGRAM SHOWING THE PROBLEM
@jmklix I have created a sample program that shows the problem. Please have a look when you get a chance.
This program uses the lex api to stream 2 minutes of audio to a lex bot (I tested using the HotelBot). The caller immediately says "I would like to book a flight". When run on Debian 11, a transcript is returned about 6 seconds after the start of the call. When run on Debian 12 the same transcript is returned after 2 minutes (!).
If I am doing something wrong, it should be easy for you to see in the sample program, but as far as I can tell I am just calling the apis.
My tests were run on AWS in us-east-1
17 remaining items