-
Notifications
You must be signed in to change notification settings - Fork 9
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(internal): Automated test of demo #211
Conversation
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
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.
There is still a failed check. Are you planning to solve or do you want me to?
Don't add bee stack. Get the failed checks fixed. Thx |
Signed-off-by: Nigel Jones <[email protected]>
I should clarify, the 'to consider' list is not for now (just input for discussion) This PR is just to understand the feasibility of automating one of the workflows that uses ollama that's been a bit problematic. Will look at schema in separate PR. |
Signed-off-by: Nigel Jones <[email protected]>
I am saying don't worry about "to consider" get this PR passing checks. And be done for now. Thx |
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.
Parts are failing but will fix this in separate PRs. Let's merge this for now. Thx
POC of running a basic demo
Based on results of this (after discussion) could consider
Other tests are also possible that stub out external calls to ollama