fix: ws.close instead of ws.terminate. Improved progress display #320
kevinwang5658Annotations
12 errors and 2 warnings
|
build-and-test (ubuntu-latest)
Process completed with exit code 1.
|
|
test/orchestrator/refresh/refresh.test.ts > Refresh orchestrator tests > Can import and update an existing project (without prompting the user)(this is the no args version):
src/plugins/resolver.ts#L83
Error: Plugin default not found and not able to download from registry. Please try again at a later time
❯ Function.resolvePluginNetwork src/plugins/resolver.ts:83:13
❯ Function.resolveAll src/plugins/resolver.ts:41:28
❯ PluginManager.initialize src/plugins/plugin-manager.ts:40:21
❯ Function.run src/common/initialize-plugins.ts:44:33
❯ Function.run src/orchestrators/refresh.ts:24:34
❯ test/orchestrator/refresh/refresh.test.ts:202:5
|
|
test/orchestrator/initialize/initialize.test.ts > Parser integration tests > Finds the correct files to initialize and initializes all files within a folder:
src/plugins/resolver.ts#L83
Error: Plugin default not found and not able to download from registry. Please try again at a later time
❯ Function.resolvePluginNetwork src/plugins/resolver.ts:83:13
❯ Function.resolveAll src/plugins/resolver.ts:41:28
❯ PluginManager.initialize src/plugins/plugin-manager.ts:40:21
❯ Function.run src/common/initialize-plugins.ts:44:33
❯ test/orchestrator/initialize/initialize.test.ts:67:61
|
|
test/orchestrator/import/import.test.ts > Import orchestrator tests > Can import a resource and only display it to the user:
src/plugins/resolver.ts#L83
Error: Plugin default not found and not able to download from registry. Please try again at a later time
❯ Function.resolvePluginNetwork src/plugins/resolver.ts:83:13
❯ Function.resolveAll src/plugins/resolver.ts:41:28
❯ PluginManager.initialize src/plugins/plugin-manager.ts:40:21
❯ Function.run src/common/initialize-plugins.ts:44:33
❯ Function.run src/orchestrators/import.ts:48:34
❯ test/orchestrator/import/import.test.ts:670:5
|
|
test/orchestrator/import/import.test.ts > Import orchestrator tests > Can import a resource and save it into an existing project:
src/plugins/resolver.ts#L83
Error: Plugin default not found and not able to download from registry. Please try again at a later time
❯ Function.resolvePluginNetwork src/plugins/resolver.ts:83:13
❯ Function.resolveAll src/plugins/resolver.ts:41:28
❯ PluginManager.initialize src/plugins/plugin-manager.ts:40:21
❯ Function.run src/common/initialize-plugins.ts:44:33
❯ Function.run src/orchestrators/import.ts:48:34
❯ test/orchestrator/import/import.test.ts:299:5
|
|
test/orchestrator/import/import.test.ts > Import orchestrator tests > Can import a resource (no project) and can save to a new file:
test/orchestrator/import/import.test.ts#L130
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/orchestrator/import/import.test.ts:130:3
|
|
test/orchestrator/edit/edit.test.ts > Edit orchestrator tests > It will start a local server on config.connectServerPort:
test/orchestrator/edit/edit.test.ts#L55
Error: connect ECONNREFUSED 127.0.0.1:51040
❯ test/orchestrator/edit/edit.test.ts:55:8
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 51040 }
Caused by: Caused by: Error: Matcher did not succeed in time.
❯ test/orchestrator/edit/edit.test.ts:51:5
|
|
test/integration/resolver.test.ts > Plugin resolver integration test > works after .DS_store exists in the plugins folder:
src/plugins/resolver.ts#L74
Error: Plugin default not found and not able to download from registry. Please try again at a later time
❯ Function.resolvePluginNetwork src/plugins/resolver.ts:74:13
❯ Function.resolveAll src/plugins/resolver.ts:41:28
❯ test/integration/resolver.test.ts:43:5
|
|
test/integration/resolver.test.ts > Plugin resolver integration test > resolves the default plugin:
src/plugins/resolver.ts#L74
Error: Plugin default not found and not able to download from registry. Please try again at a later time
❯ Function.resolvePluginNetwork src/plugins/resolver.ts:74:13
❯ Function.resolveAll src/plugins/resolver.ts:41:28
❯ test/integration/resolver.test.ts:21:5
|
|
Unhandled error:
src/utils/spawn.ts#L43
Error: Password must be specified!
❯ spawnSafe src/utils/spawn.ts:43:11
❯ spawn src/utils/spawn.ts:32:29
❯ installDesktopApp src/utils/desktop-installer.ts:101:13
❯ Function.run src/orchestrators/edit.ts:29:9
This error originated in "test/orchestrator/edit/edit.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "It will start a local server on config.connectServerPort". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
build-and-test (macos-latest)
The strategy configuration was canceled because "build-and-test.ubuntu-latest" failed
|
|
build-and-test (macos-latest)
The operation was canceled.
|
|
build-and-test (ubuntu-latest)
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/
|
|
build-and-test (macos-latest)
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/
|