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
Assertion and query will fail if OPENAI_API_KEY is set but empty, ex.: OPENAI_API_KEY="" will create an assertion failed error however this error doesn't happen when using ai Action or Action (this happens both in chrome playground and using the bridge connector from ts).
Error:
Playground:
Assertion failed: there are some search results
Reason: Cannot find config for AI model service. You should set it before using. https://midscenejs.com/model-provider.html
CMD TSX
/node_modules/@midscene/web/dist/lib/bridge-mode.js:1598
throw new Error(`${errMsg}
^
Error: Assertion failed: there are some search results
Reason: Cannot find config for AI model service. You should set it before using. https://midscenejs.com/model-provider.html
at AgentOverChromeBridge.aiAssert (/node_modules/@midscene/web/dist/lib/bridge-mode.js:1598:13)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async <anonymous> (/demo.tsx:17:5)
In both cases it works for the action run as expected (as I'm using my own openai backend and it doesn't require openai api key) but it breaks for query and assert
The text was updated successfully, but these errors were encountered:
@jxoir The document here includes configuration instructions. Additionally, you can test your OpenAI parameter connectivity using our test project: connectivity test.
Assertion and query will fail if OPENAI_API_KEY is set but empty, ex.: OPENAI_API_KEY="" will create an assertion failed error however this error doesn't happen when using ai Action or Action (this happens both in chrome playground and using the bridge connector from ts).
Error:
CMD TSX
In both cases it works for the action run as expected (as I'm using my own openai backend and it doesn't require openai api key) but it breaks for query and assert
The text was updated successfully, but these errors were encountered: