-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat: conversational pipeline (demo) #324
base: main
Are you sure you want to change the base?
Conversation
Code Coverage Summary
Diff against main
Results for commit: 76ba27e Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Trivy scanning results. .venv/lib/python3.10/site-packages/PyJWT-2.9.0.dist-info/METADATA (secrets)Total: 1 (MEDIUM: 1, HIGH: 0, CRITICAL: 0) MEDIUM: JWT (jwt-token) .venv/lib/python3.10/site-packages/litellm/llms/huggingface/huggingface_llms_metadata/hf_text_generation_models.txt (secrets)Total: 1 (MEDIUM: 0, HIGH: 0, CRITICAL: 1) CRITICAL: HuggingFace (hugging-face-access-token) .venv/lib/python3.10/site-packages/litellm/proxy/_types.py (secrets)Total: 1 (MEDIUM: 1, HIGH: 0, CRITICAL: 0) MEDIUM: Slack (slack-web-hook) |
@ludwiktrammer that's rad, I really like how it looks 🎉 |
I think ConversationPipeline should have base class with common interface. Thiw will allow users to have their fully custom pipeline, just ensuring that input / output can be handled by other ragbits components. This will allow us to easily expose any predefined / user custom-defined conversation pipeline through common API (for example to connect it with our demo frontend app). |
I'm wondering if we can simplify interface of the plugins. Right now they can serve two main functionalities:
What if we could say that plugin just have one method called
and probably if we say that StateToChat / LLM are also on the same level then we'll have
|
No description provided.