Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not responding forever until you press Ctrl-C #21

Open
sloganking opened this issue Feb 28, 2024 · 2 comments
Open

Not responding forever until you press Ctrl-C #21

sloganking opened this issue Feb 28, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@sloganking
Copy link
Owner

The assistant does not display the text that the user made and never generates tokens for a response. For some reason, pressing Ctrl-C on the terminal fixes this and causes the assistant to display what the user spoke and respond to it in text and speech.

@sloganking sloganking added the bug Something isn't working label Feb 28, 2024
@sloganking
Copy link
Owner Author

image
Here it didn't respond until Ctrl-C was pressed. Afterwards it said "recording too short" a bunch, even though those recording attempts were definitely long enough when I made them. So something stopped the key press event handling thread.

@sloganking
Copy link
Owner Author

I added logs, which will help in debugging this issue, and I have captured at least one implementation of this issue, and here are the results.
image

The application seems to freeze upon transcribing user audio and never exits. However, the RDEV thread sending keypresses and the audio recording thread starting and stopping recording audio files is still working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant