Dylan Frendo

No, the function was a normal balance query and the data is still correct, just stored in the wrong variable.

@Reecepbcups Looking more into it, it seems that [SerializeCosmosResponse](https://github.com/cosmos/ibc-apps/blob/modules/async-icq/v7.1.1/modules/async-icq/keeper/relay.go#L75) is returning different bytes between the two versions. We checked the data in this [unit test](https://github.com/cosmos/ibc-apps/blob/modules/async-icq/v7.1.1/modules/async-icq/keeper/relay_test.go#L33). v7.0.0 returns `eyJkYXRhIjoiQ2dRNkFoSUEifQ==` v7.1.1 returns...

So you always need to have the docker compose files in the same directory for it to work? I think it's useful if you can specify different paths to build...

i already did as mentioned in the issue itself ``` const environment = await new DockerComposeEnvironment( PROJECT_ROOT, ["./lib/rollup/docker/docker-compose.yml", "./docker/docker-compose.yml"] ) .withBuild() .up(); ``` which gives the error `failed to solve:...

``` PROJECT_ROOT/ ├── docker/ │ ├── docker-compose.yml │ ├── docker.ethereum.Dockerfile │ └── docker.ignition.Dockerfile │ └── lib/ └── rollup/ └── docker/ ├── fuel_committer/ ├── fuel_node/ ├── sequencer/ ├── docker-compose.yml ├── docker.eth_node.Dockerfile...