Metadata file for `GITHUB_ISSUES_GET` not found
Trying to run SWE agent, I have set my GITHUB, composio, and e2b API keys, and I have already run composio apps update.
Error: Error while executing github_issues_get: Metadata file for GITHUB_ISSUES_GET not found, Please run composio apps update to fix this
at E2BWorkspace.executeAction (/home/page/Documents/Dev/swe-js-1/node_modules/composio-core/src/env/base.ts:224:15)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at githubIssueValidator (/home/page/Documents/Dev/swe-js-1/src/utils.ts:50:28)
at fromGithub (/home/page/Documents/Dev/swe-js-1/src/utils.ts:77:48)
at main (/home/page/Documents/Dev/swe-js-1/src/app.ts:12:27)
[ERROR] 12:39:01 Error: Error while executing github_issues_get: Metadata file for GITHUB_ISSUES_GET not found, Please run composio apps update to fix this
^C
page@page:~/Documents/Dev/swe-js-1$ composio apps update
⚠️ Apps does not require update
⚠️ Tags does not require update
⚠️ Actions does not require update
⚠️ Triggers does not require update3 Replies
quickest-silverOP•6mo ago
I also notice, even though COMPOSIO_API_KEY is set, the logging reports a 'null':
[DEBUG] 12:41:31 PM Creating workspace with env=E2B and kwargs={"apiKey":"e2b_redacted_jhu","composioBaseURL":"https://backend.composio.dev/","composioAPIKey":null}
composio add github
opens a browser window even though I have my COMPOSIO_API_KEY var set and exported. How can I diagnose this further?
I also notice I have two connections for each, and I did not setup any discord connection, despite it showing two of them here:
composio connections
• Id : redacted
App: github
• Id : redacted
App: github
• Id : redacted
App: discord
• Id : redacted
App: discordLet me quickly take a look.
What's your email for the account?
Can you dm me.
Also,
you can use
--no-browser option to not open browser.
composio add github --no-browserdeep-jade•5mo ago
Hey @pager, is it working good for you??