From a471213458be375f717f6386e578385ea07ea5ca Mon Sep 17 00:00:00 2001 From: 6r1d Date: Thu, 9 Nov 2023 17:15:59 +0200 Subject: [PATCH] [docs]: add SCALE codec troubleshooting section (#428) Signed-off-by: 6r1d --- .../troubleshooting/configuration-issues.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/src/guide/troubleshooting/configuration-issues.md b/src/guide/troubleshooting/configuration-issues.md index 9617122d0..d0b9fb214 100644 --- a/src/guide/troubleshooting/configuration-issues.md +++ b/src/guide/troubleshooting/configuration-issues.md @@ -96,3 +96,22 @@ account_ either, unless you submit an instruction. These sorts of subtle mistakes can be avoided, for example, by deserialising directly from string literals, or by generating a fresh key-pair in places where it makes sense. + +## SCALE codec errors + +You may encounter the SCALE codec errors when there's a discrepancy +between how the data is structured on the client side and the peer side. + +In case you're using `iroha_client_cli` and rebuild it inside the Iroha +project directory root: + +* `rm ./target/debug/iroha_client_cli ./target/release/iroha_client_cli` +* `cargo build -p iroha_client_cli` + +The reason to do so is that it's easy to confuse the builds in +the `debug` and `release` directories and keep using an old build. + +Alternatively, please compare the output of +`/target/debug/iroha_client_cli --version` with a version in the Iroha log. +You need to view the part at which the Iroha peer starts. +This will allow you to see whether the versions match.