Shunkichi Sato

The [transaction lifecycle feature](https://github.com/hyperledger/iroha/issues/2478) will affect the implementation of this issue

After thinking, I'd suggest to separate transaction build from submission, because "submit then calculate hash" would not give clients time to subscribe events specifying the hash

```bash bash 2690-inspect.sh before >before.log ``` ```bash bash 2690-inspect.sh fixme >fixme.log ``` 2690-inspect.sh ```bash #!/bin/bash set -eu # configure ISSUE=2690 TOOLCHAINS=() case $1 in before) COMMIT='70e782bb' STAGE_BASE='rust-base' STAGE_BUILD='builder' TOOLCHAINS+=('stable') TOOLCHAINS+=('nightly-2022-04-20')...

Clues, or might be misleads: - https://docs.docker.com/desktop/mac/apple-silicon/ - The causative commit 162d8e86 introduced `x86_64-unknown-linux-musl` as a build target - https://docs.docker.com/engine/reference/commandline/buildx_build/#platform

[Removing the need for the base image](https://github.com/hyperledger/iroha/issues/2732#issuecomment-1244959820) first would simplify this issue and reduce most of the subsequent tasks. In that case, developers and CI will respectively have their own...

There have been no recent commits to docker files that would resolve this issue. Do you think something has changed locally @Arjentix ?

> As another issue, the published final image should be checked if it works in M1. I meant after the local build is resolved, the corresponding remote build result will...

> do you suggest to cache the whole CI image with all rustup and cargo dependencies? Yes, in the sense of replacing the base image @BAStos525 However, there are no...

Could be replaced by #1455 in the future

Results of [the failing test command](https://github.com/hyperledger/iroha/blob/88c5290cf34d8a35915d966a5737161bfdfb4546/.github/workflows/iroha2-dev-pr.yml#L66 ) in my local at 88c5290c: - When I run ```bash cargo llvm-cov --lib --no-report --all-features --workspace --no-fail-fast ``` , the error is reproducible....