AAP-55681: Bump lightspeed-core-stack and lightspeed-providers #107
Conversation
lightspeed-stack-mcp.yaml
Outdated
| user_data_collection: | ||
| feedback_disabled: true | ||
| transcripts_disabled: true | ||
| user_data_collection: {} |
There was a problem hiding this comment.
@jameswnl Pydantic is blocking both fields to change.
I will check if there is a way to set it in a different way
There was a problem hiding this comment.
@jameswnl so they changed the fields, I will push the changes to add these again
I check if the changes hasn't impact the chatbot
There was a problem hiding this comment.
so the setting fields are the opposite now:
feedback_enabled: false
transcripts_enabled: false
| type: sqlite | ||
| namespace: null | ||
| db_path: ${env.PROVIDERS_DB_DIR:=/.llama/data/distributions/ansible-chatbot}/localfs_datasetio.db | ||
| files: |
There was a problem hiding this comment.
this files is missing in the apis section, expected?
There was a problem hiding this comment.
@jameswnl yes, that required now, that why we added these
There was a problem hiding this comment.
do we need to add an entry of files to the section from Line 4 - 11?
There was a problem hiding this comment.
nice catch! I will add it
the weird part that LCS hasn't complained about it
fyi, the error I got
RuntimeError: Failed to resolve 'tool_runtime' provider 'rag-runtime' of type 'inline::rag-runtime': required dependency 'files' is not available. Please add a 'files' provider to your configuration or check if the provider is properly configured.
bump lightspeed-providers to 0.1.6
de1987
force-pushed
the
aap-55681-bump-lcs-and-lightspeed-providers
branch
from
3d164ad to
37d526e
Compare
2 participants
Jira Issue: AAP-55681
Description
To support the 3rd party models it's required to:
lightspeed-core-stackto 0.3.0lightspeed-providersto 0.1.6Testing
Steps to test
make cleanmake runScenarios tested
I run the chatbox locally with Granite 3.3 and asked at least 20 questions about AAP, playbooks, how to automate things... All the responses were as expected.
Production deployment