Skip to content

chore: add cargo-deny to codebase #245

chore: add cargo-deny to codebase

chore: add cargo-deny to codebase #245

Triggered via pull request September 20, 2024 09:08
@ntn-x2ntn-x2
synchronize #732
aa/vuln-check
Status Failure
Total duration 1h 24m 58s
Artifacts

check-code.yml

on: pull_request
Get HEAD commit message
5s
Get HEAD commit message
Matrix: Run Clippy checks
Check formatting
1m 29s
Check formatting
Check cargo-deny rules
1m 37s
Check cargo-deny rules
Run Chopsticks tests
1h 19m
Run Chopsticks tests
Matrix: Check Rustdoc
Matrix: Run Cargo tests
Matrix: Run try-runtime
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 54 warnings
Run try-runtime (spiritnet)
Process completed with exit code 101.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents ❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19 ❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44 ❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47 ❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207: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 "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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js#L85
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/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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents ❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19 ❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44 ❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47 ❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207: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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js#L85
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 This error originated in "src/tests/switchPallet/trappedAssets.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 "Trapped assets". 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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents ❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19 ❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44 ❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47 ❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13 This error originated in "src/tests/switchPallet/fullFlowSwitch.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 "Full e2e tests". 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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js#L11
ConnectionIsNotSetError: Connection with sqlite database is not established. Check connection configuration. ❯ SqliteQueryRunner.query src/driver/sqlite/SqliteQueryRunner.ts:71:19 ❯ SqliteQueryRunner.startTransaction src/driver/sqlite-abstract/AbstractSqliteQueryRunner.ts:112:24 ❯ EntityManager.transaction src/entity-manager/EntityManager.ts:153:13 ❯ SqliteDatabase.saveBlock node_modules/@acala-network/chopsticks-db/dist/esm/base-sql.js:11:9 ❯ Blockchain.saveBlockToDB node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:130:13 ❯ Blockchain.onNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/index.js:246:9 ❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:249:9 ❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13 This error originated in "src/tests/switchPallet/fullFlowSwitch.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 "Full e2e tests". 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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents ❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19 ❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44 ❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47 ❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13 This error originated in "src/tests/switchPallet/relayToken.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 DOTs from basilisk 2 Peregrine". 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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js#L193
Error: Failed to apply inherents ❯ initNewBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:193:19 ❯ Module.buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/block-builder.js:300:44 ❯ TxPool.#buildBlock node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:223:47 ❯ TxPool.#buildBlockIfNeeded node_modules/@acala-network/chopsticks-core/dist/esm/blockchain/txpool.js:207:13 This error originated in "src/tests/switchPallet/switchEkiltAgainstKilt.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 ePILTs against PILTS on Peregrine". 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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Limited Reserve V4 Transfers from AssetHub Account Alice -> Peregrine Account Bob > sender AssetHub::polkadotXcm::[FeesPaid,Attempted,Sent] 1` mismatched - Expected + Received @@ -3,11 +3,11 @@ "data": { "outcome": { "Complete": { "used": { "proofSize": "(rounded 6200)", - "refTime": "(rounded 290000000)", + "refTime": "(rounded 300000000)", }, }, }, }, "method": "Attempted", @@ -16,11 +16,11 @@ { "data": { "fees": [ { "fun": { - "Fungible": "(rounded 310000000)", + "Fungible": "(rounded 300000000)", }, "id": { "interior": "Here", "parents": 1, }, ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 This error originated in "src/tests/xcm/assetHub/peregrine/limitedReserveTransferAssetHubPeregrine.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 V4 Transfers from AssetHub Account Alice -> Peregrine Account Bob". 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.
Unhandled error: integration-tests/chopsticks/node_modules/@acala-network/chopsticks-testing/dist/esm/check.js#L163
Error: Snapshot `Limited Reserve V4 Transfers from AssetHub Account Alice -> Peregrine Account Bob > sender AssetHub::balances::[Withdraw] 1` mismatched - Expected + Received @@ -1,9 +1,9 @@ [ { "data": { - "amount": "(rounded 24000000)", + "amount": "(rounded 12000000)", "who": "15jSz35ugoWTc61xHPoxEkHte4o7UanKCk1gx1dizA8yuNs8", }, "method": "Withdraw", "section": "balances", }, ❯ Checker.toMatchSnapshot node_modules/@acala-network/chopsticks-testing/dist/esm/check.js:163:51 This error originated in "src/tests/xcm/assetHub/peregrine/limitedReserveTransferAssetHubPeregrine.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 V4 Transfers from AssetHub Account Alice -> Peregrine Account Bob". 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.
Run Clippy checks
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
Run Clippy checks
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
Run Clippy checks (--all-features)
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
Check Rustdoc (--all-features)
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
Check Rustdoc
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
Run try-runtime (peregrine)
The command [sudo apt-get clean] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding...
Run try-runtime (spiritnet)
The command [sudo apt-get clean] failed to complete successfully. Proceeding...