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

Flush upon finishing inference #811

Merged
merged 1 commit into from Apr 23, 2023

Conversation

tarasglek
Copy link
Contributor

Was trying to parse when inference was complete, realized that \n is that signal, but without this flush it doesn't get flushed until next inference has ran.

Eg before this we'd get

"\u001b[2K\r                                                                                                    \u001b[2K\r I want to figure out what's up with these new lines.",
"\n\u001b[2K\r                                                                                                    \u001b[2K\r (upbeat music)"

Now it should be

"\u001b[2K\r                                                                                                    \u001b[2K\r I want to figure out what's up with these new lines.",
"\n",
"\u001b[2K\r                                                                                                    \u001b[2K\r (upbeat music)"

Note markdown fails to render so here is a screenshot of markdown:
image

@ggerganov ggerganov merged commit 02ec83c into ggerganov:master Apr 23, 2023
@tarasglek tarasglek deleted the taras/flush-when-complete branch April 24, 2023 11:48
jacobwu-b pushed a commit to jacobwu-b/Transcriptify-by-whisper.cpp that referenced this pull request Oct 24, 2023
jacobwu-b pushed a commit to jacobwu-b/Transcriptify-by-whisper.cpp that referenced this pull request Oct 24, 2023
landtanin pushed a commit to landtanin/whisper.cpp that referenced this pull request Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants