From ec2e888502408b7564f81341898c00417a2160ad Mon Sep 17 00:00:00 2001 From: Guilherme Dantas Date: Wed, 24 May 2023 11:05:26 -0300 Subject: [PATCH] fix(contracts): do not format `finish_epoch_reponse.json` * We used to format the JSON returned by the machine with `jq` to make git diffs smoother (fewer changed lines). But since now we are not committing this file anymore, it no longer makes no sense to format it with `jq`. This has no impact on the behaviour of the proof generation system, as `jq` only changes formatting, not the data. --- onchain/rollups/test/foundry/dapp/helper/update-proofs.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/onchain/rollups/test/foundry/dapp/helper/update-proofs.sh b/onchain/rollups/test/foundry/dapp/helper/update-proofs.sh index 089aefd5..bf5fbfe9 100755 --- a/onchain/rollups/test/foundry/dapp/helper/update-proofs.sh +++ b/onchain/rollups/test/foundry/dapp/helper/update-proofs.sh @@ -57,9 +57,8 @@ runmachine() { } # Decode strings in epoch status from Base64 to hexadecimal -# Format the output with jq so that git diffs are smoother b64to16() { - python3 -m b64to16 output/finish_epoch_response_64.json | jq > finish_epoch_response.json + python3 -m b64to16 output/finish_epoch_response_64.json > finish_epoch_response.json } # Generate Solidity libraries with proofs from epoch status