ConnectionIsNotSetError: Connection with sqlite database is not established. Check connection configuration. ❯ SqliteQueryRunner.query src/driver/sqlite/SqliteQueryRunner.ts:71:19 ❯ SelectQueryBuilder.loadRawResults src/query-builder/SelectQueryBuilder.ts:3805:43 ❯ SelectQueryBuilder.executeEntitiesAndRawResults src/query-builder/SelectQueryBuilder.ts:3551:37 ❯ SelectQueryBuilder.getRawAndEntities src/query-builder/SelectQueryBuilder.ts:1670:40 ❯ SelectQueryBuilder.getOne src/query-builder/SelectQueryBuilder.ts:1697:36 ❯ EntityManager.findOne src/entity-manager/EntityManager.ts:1215:14 ❯ Repository.findOne src/repository/Repository.ts:597:29 ❯ SqliteDatabase.queryStorage node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:85:69 ❯ RemoteStorageLayer.get node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:32:25 ❯ Block.get node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block.js:118:21 This error originated in "src/tests/switchPallet/pauseSwitch.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 "Withdraw ROCs while switch is paused". 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.

ConnectionIsNotSetError: Connection with sqlite database is not established. Check connection configuration. ❯ SqliteQueryRunner.query src/driver/sqlite/SqliteQueryRunner.ts:71:19 ❯ SelectQueryBuilder.loadRawResults src/query-builder/SelectQueryBuilder.ts:3805:43 ❯ SelectQueryBuilder.executeEntitiesAndRawResults src/query-builder/SelectQueryBuilder.ts:3551:37 ❯ SelectQueryBuilder.getRawAndEntities src/query-builder/SelectQueryBuilder.ts:1670:40 ❯ SelectQueryBuilder.getOne src/query-builder/SelectQueryBuilder.ts:1697:36 ❯ EntityManager.findOne src/entity-manager/EntityManager.ts:1215:14 ❯ Repository.findOne src/repository/Repository.ts:597:29 ❯ SqliteDatabase.queryStorage node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:85:69 ❯ RemoteStorageLayer.get node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/storage-layer.js:32:25 ❯ Block.get node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block.js:118:21 This error originated in "src/tests/switchPallet/pauseSwitch.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 "Withdraw ROCs while switch is paused". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::xcmpQueue::[XcmpMessageSent] 2` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::assetSwitchPool1::[LocalToRemoteSwitchExecuted] 2` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::balances::[Transfer] 2` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::xcmpQueue::[XcmpMessageSent] 3` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::assetSwitchPool1::[LocalToRemoteSwitchExecuted] 3` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::balances::[Transfer] 3` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::xcmpQueue::[XcmpMessageSent] 4` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

Error: Snapshot `Switch KILTs against EKILTs no enough DOTs on AH > sender Peregrine::assetSwitchPool1::[LocalToRemoteSwitchExecuted] 4` mismatched ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 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 "Switch KILTs against EKILTs no enough DOTs on AH". 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.

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.