feat(tiles-server): add tileset MCP server #126
ci.yml
on: pull_request
Build CesiumJS MCP Servers
1m 3s
Build MCP Apps Servers
24s
Build Geolocation MCP Server
19s
Annotations
10 errors and 3 warnings
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_remove command > should remove tileset by name:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L294
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:294:30
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_remove command > should remove tileset by tilesetId:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L280
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:280:30
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > concurrent add operations > should handle multiple concurrent adds:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L241
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:241:49
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > error cases > should fail when url source type has no url:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L209
AssertionError: expected 'Cannot read properties of undefined (…' to contain 'Cannot load tileset'
Expected: "Cannot load tileset"
Received: "Cannot read properties of undefined (reading 'fromUrl')"
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:209:30
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > url source type > should handle URLs with query parameters:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L197
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:197:32
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > url source type > should add a url-based tileset successfully:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L183
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:183:32
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > ion source type > should use sourceType as default name:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L170
AssertionError: expected undefined to be 'ion' // Object.is equality
- Expected:
"ion"
+ Received:
undefined
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:170:29
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > ion source type > should handle tileset visibility setting:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L160
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:160:32
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > ion source type > should generate sequential tileset IDs:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L148
AssertionError: expected undefined to be 'ts-1' // Object.is equality
- Expected:
"ts-1"
+ Received:
undefined
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:148:35
|
|
test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts > Tiles Manager Unit Tests > tileset_add command > ion source type > should add an ion tileset successfully:
mcp/cesium-js/test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts#L127
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ test-applications/packages/client-core/test/unit/tiles-manager.unit.test.ts:127:32
|
|
Build Geolocation MCP Server
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, pnpm/action-setup@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/
|
|
Build MCP Apps Servers
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, pnpm/action-setup@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/
|
|
Build CesiumJS MCP Servers
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, pnpm/action-setup@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/
|