CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. ❯ DataSource.destroy src/data-source/DataSource.ts:306:19 ❯ SqliteDatabase.close node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:6:18 ❯ Blockchain.close node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:426:9 ❯ close node_modules/@acala-network/chopsticks/dist/esm/setup-with-server.js:17:13 ❯ Object.teardown node_modules/@acala-network/chopsticks-utils/dist/esm/index.js:76:13 This error originated in "src/tests/switchPallet/switchConfig.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 "Send eKILT from other reserve location". 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.

CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. ❯ DataSource.destroy src/data-source/DataSource.ts:306:19 ❯ SqliteDatabase.close node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:6:18 ❯ Blockchain.close node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:426:9 ❯ close node_modules/@acala-network/chopsticks/dist/esm/setup-with-server.js:17:13 ❯ Object.teardown node_modules/@acala-network/chopsticks-utils/dist/esm/index.js:76:13 This error originated in "src/tests/switchPallet/switchConfig.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 "Send eKILT from other reserve location". 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.

CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. ❯ DataSource.destroy src/data-source/DataSource.ts:306:19 ❯ SqliteDatabase.close node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:6:18 ❯ Blockchain.close node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:426:9 ❯ close node_modules/@acala-network/chopsticks/dist/esm/setup-with-server.js:17:13 ❯ Object.teardown node_modules/@acala-network/chopsticks-utils/dist/esm/index.js:76:13 This error originated in "src/tests/xcm/hydration/limitedReseveTransferHydraDxSpiritnet.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 "Limited Reserve Transfers from HydraDx Account Alice -> Spiritnet Account Alice". 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.

CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. ❯ DataSource.destroy src/data-source/DataSource.ts:306:19 ❯ SqliteDatabase.close node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:6:18 ❯ Blockchain.close node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:426:9 ❯ close node_modules/@acala-network/chopsticks/dist/esm/setup-with-server.js:17:13 ❯ Object.teardown node_modules/@acala-network/chopsticks-utils/dist/esm/index.js:76:13 This error originated in "src/tests/xcm/hydration/limitedReseveTransferHydraDxSpiritnet.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 "Limited Reserve Transfers from HydraDx Account Alice -> Spiritnet Account Alice". 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.

CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. ❯ DataSource.destroy src/data-source/DataSource.ts:306:19 ❯ SqliteDatabase.close node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:6:18 ❯ Blockchain.close node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:426:9 ❯ close node_modules/@acala-network/chopsticks/dist/esm/setup-with-server.js:17:13 ❯ Object.teardown node_modules/@acala-network/chopsticks-utils/dist/esm/index.js:76:13 This error originated in "src/tests/xcm/assetHub/spiritnet/teleportTransferSpiritnetAssetHub.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 "Teleport assets from Spiritnet Account Alice -> AH Account Alice". 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.

CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. ❯ DataSource.destroy src/data-source/DataSource.ts:306:19 ❯ SqliteDatabase.close node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:6:18 ❯ Blockchain.close node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:426:9 ❯ close node_modules/@acala-network/chopsticks/dist/esm/setup-with-server.js:17:13 ❯ Object.teardown node_modules/@acala-network/chopsticks-utils/dist/esm/index.js:76:13 This error originated in "src/tests/xcm/assetHub/spiritnet/teleportTransferSpiritnetAssetHub.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 "Teleport assets from Spiritnet Account Alice -> AH Account Alice". 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.

Process completed with exit code 1.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.