feat(opencode): support multiple managed MCP servers via MCP_URL_* env #37
JohanYPAnnotations
8 errors and 2 warnings
|
Lint, Build, Test (Node 22)
Process completed with exit code 1.
|
|
tests/bot/handlers/prompt.test.ts > bot/handlers/prompt > starts prompts through promptAsync instead of the streaming prompt endpoint:
tests/bot/handlers/prompt.test.ts#L227
AssertionError: expected "spy" to be called with arguments: [ { sessionID: 'session-1', …(5) } ]
Received:
1st spy call:
@@ -6,11 +6,13 @@
"modelID": "gpt-5",
"providerID": "openai",
},
"parts": [
{
- "text": "Review README",
+ "text": "[Channel: telegram]
+
+ Review README",
"type": "text",
},
],
"sessionID": "session-1",
"variant": "default",
Number of calls: 1
❯ tests/bot/handlers/prompt.test.ts:227:43
|
|
tests/bot/commands/rename.test.ts > bot/commands/rename > renames session on valid text and clears states:
tests/bot/commands/rename.test.ts#L126
AssertionError: expected "spy" to be called with arguments: [ { id: 'session-1', …(2) } ]
Received:
1st spy call:
@@ -1,6 +1,7 @@
[
+ "telegram",
{
"directory": "D:/repo",
"id": "session-1",
"title": "New title",
},
Number of calls: 1
❯ tests/bot/commands/rename.test.ts:126:42
|
|
Lint, Build, Test (Node 20)
Process completed with exit code 1.
|
|
tests/bot/handlers/prompt.test.ts > bot/handlers/prompt > starts prompts through promptAsync instead of the streaming prompt endpoint:
tests/bot/handlers/prompt.test.ts#L227
AssertionError: expected "spy" to be called with arguments: [ { sessionID: 'session-1', …(5) } ]
Received:
1st spy call:
@@ -6,11 +6,13 @@
"modelID": "gpt-5",
"providerID": "openai",
},
"parts": [
{
- "text": "Review README",
+ "text": "[Channel: telegram]
+
+ Review README",
"type": "text",
},
],
"sessionID": "session-1",
"variant": "default",
Number of calls: 1
❯ tests/bot/handlers/prompt.test.ts:227:43
|
|
tests/bot/commands/rename.test.ts > bot/commands/rename > renames session on valid text and clears states:
tests/bot/commands/rename.test.ts#L126
AssertionError: expected "spy" to be called with arguments: [ { id: 'session-1', …(2) } ]
Received:
1st spy call:
@@ -1,6 +1,7 @@
[
+ "telegram",
{
"directory": "D:/repo",
"id": "session-1",
"title": "New title",
},
Number of calls: 1
❯ tests/bot/commands/rename.test.ts:126:42
|
|
tests/mcp/memory-server.test.ts > mcp/memory-server > task tools > task_delete removes the row and returns ok:
tests/mcp/memory-server.test.ts#L658
AssertionError: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ tests/mcp/memory-server.test.ts:658:26
|
|
tests/mcp/memory-server.test.ts > mcp/memory-server > task tools > task_list filters by type:
src/scheduled-task/next-run.ts#L285
Error: Unable to compute next cron run for expression: 0 0 * * 0
❯ computeNextCronRunAt src/scheduled-task/next-run.ts:285:9
❯ buildScheduledTask src/scheduled-task/builder.ts:134:17
❯ executeToolCall src/mcp/memory-server.ts:743:16
❯ handleRequest src/mcp/memory-server.ts:439:20
❯ callTool tests/mcp/memory-server.test.ts:26:5
❯ tests/mcp/memory-server.test.ts:624:15
|
|
Lint, Build, Test (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint, Build, Test (Node 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|