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
import { MultiAgentOrchestrator } from "multi-agent-orchestrator";
const orchestrator = new MultiAgentOrchestrator();
orchestrator.addAgent(agent);
const response = await orchestrator.routeRequest(
"I need help with my order",
"user123",
"session456"
);
processing request: TypeError: (0 , MGt.setCredentialFeature) is not a function
at /var/task/index.js:12:34655
at e (/var/task/index.js:35:243)
at /var/task/index.js:1:38819
at coalesceProvider (/var/task/index.js:1:38997)
at /var/task/index.js:1:39199
at /var/task/node_modules/@smithy/core/dist-cjs/index.js:82:23
at async /var/task/index.js:1:7657
at async Oee.processRequest (/var/task/index.js:158:4342)
at async Oee.classify (/var/task/index.js:157:76)
at async o1e.routeRequest (/var/task/index.js:249:5168)
Expected Behaviour
https://awslabs.github.io/multi-agent-orchestrator/agents/built-in/lambda-agent/
Following instruction from this link should work.
Current Behaviour
import { MultiAgentOrchestrator } from "multi-agent-orchestrator";
const orchestrator = new MultiAgentOrchestrator();
orchestrator.addAgent(agent);
const response = await orchestrator.routeRequest(
"I need help with my order",
"user123",
"session456"
);
processing request: TypeError: (0 , MGt.setCredentialFeature) is not a function
at /var/task/index.js:12:34655
at e (/var/task/index.js:35:243)
at /var/task/index.js:1:38819
at coalesceProvider (/var/task/index.js:1:38997)
at /var/task/index.js:1:39199
at /var/task/node_modules/@smithy/core/dist-cjs/index.js:82:23
at async /var/task/index.js:1:7657
at async Oee.processRequest (/var/task/index.js:158:4342)
at async Oee.classify (/var/task/index.js:157:76)
at async o1e.routeRequest (/var/task/index.js:249:5168)
Code snippet
Possible Solution
No response
Steps to Reproduce
try to run the code in a lambda runtime.
Tried in both node16 and 18. Both have same issues.
The text was updated successfully, but these errors were encountered: