-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
enhancement: non-english youtube rag #1960
Comments
tjbck
changed the title
Youtube video with non-english generated transcription fails to fetch
enhancement: non-english youtube rag
May 4, 2024
Merged
I've updated but I always get a similar error |
@grigio You're still requesting |
Thanks, it works. I was thinking that it was managed by the UI language |
What about trying to make a separate toggle with automatic language recognition? With the code suggested by me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Description
Bug Summary:
If you use RAG for youtube without english translation, but with another language provided- request fails with an error from
youtube-transcript-api
Steps to Reproduce:
try to execute next prompt
#https://www.youtube.com/watch?v=FuRem6-sTmQ
Expected Behavior:
prefetch the list of languages of the video from the same package with
Actual Behavior:
See the toast error after several seconds.
Environment
Open WebUI Version: 0.1.123
Ollama (if applicable): 0.1.32
Operating System: Fedora 39 (both client and server, different machines)
Browser (if applicable): Chrome (version doesn't matter)
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
I'll provide if needed, seems irrelevant
Docker Container Logs:
I'll provide if needed, seems irrelevant
Screenshots (if applicable):
Installation Method
Docker
Additional Information
The problem is that YoutubeLoader from langchain doesn't handle by himselves the verification that requested (or default
'en'
) language is provided by the video. We need to handle it by ourselves.The text was updated successfully, but these errors were encountered: