-
Notifications
You must be signed in to change notification settings - Fork 18
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: enable weaviate usage in codegate #128
Conversation
9446ad2
to
610f925
Compare
0f1997e
to
078f99a
Compare
from src.codegate.utils.utils import generate_vector_string | ||
|
||
|
||
class CodegateContextRetriever(PipelineStep): | ||
""" | ||
Pipeline step that adds a context message to the completion request when it detects | ||
the word "codegate" in the user message. | ||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question from @lukehinds on the duplicated PR #133:
Would like to understand this a little better, does it mean we only report on MAL pkgs if someone says 'codegate', what does the word trigger?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jhrozek as you proposed that system... I believe that the codegate word Will be prepended automatically ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was just an example. We need to figure out when do we trigger the RAG. With the Go implementation we did that on all conversations that had no code snippets, which is an easy implementation. We could do that for a start, but the downside was that the RAG was called also if the user didn't ask about any package. For example if they asked "give me an example SQL query" the RAG would match all packages with the word SQL in it. It would be nice to work together with @ptelang to figure out how to fine tune this.
Closes: #63