You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
I was unable to successfully execute any examples using gemini or ollama. I tried changing the ollama path as suggested in another issue, but in both cases, I encountered the same issue. For example, when running the agents or chain of thought examples, I frequently see this message: User: Instructions: Output must include: Reason:, Answer:
But eventually, it ends with the following error:
throw new Error(`Unable to fix validation error: ${err?.message}`);
^
Error: Unable to fix validation error: Output must include: `Reason:`, `Answer:`
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
This issue occurs consistently with the provided examples. I attempted to follow solutions mentioned in related issues but was unable to resolve the problem. Additional context or suggestions to fix this would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
I was unable to successfully execute any examples using
gemini
orollama
. I tried changing theollama
path as suggested in another issue, but in both cases, I encountered the same issue. For example, when running the agents or chain of thought examples, I frequently see this message:User: Instructions: Output must include: Reason:, Answer:
But eventually, it ends with the following error:
This issue occurs consistently with the provided examples. I attempted to follow solutions mentioned in related issues but was unable to resolve the problem. Additional context or suggestions to fix this would be greatly appreciated.
The text was updated successfully, but these errors were encountered: