bug(forge script): Failure on receiving a receipt, server returned a null response when a non-null response was expected

[Aliceonly]

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

uses: foundry-rs/foundry-toolchain@v1

What command(s) is the bug in?

forge script

Operating System

Linux

Describe the bug

I run workflow on ubuntu-22.04
there're like 100+ txs in script

      - name: Install Foundry
        uses: foundry-rs/foundry-toolchain@v1

          forge script script/deploy.s.sol:DeployScript \
            --slow \
            --rpc-url ${{ env.RPC }} \
            --private-key ${{ secrets.PRIVATE_KEY }} \
            --broadcast \

always got error:

Error: Failure on receiving a receipt for 0x37949a9954e1....d679f0a8601879c5bc314bceee8:
server returned a null response when a non-null response was expected

 Add `--resume` to your command to try and continue broadcasting
        the transactions.

but tx has been comfirmed onchain, also I tried serval rpcs and failed

[Aliceonly]

tryna add --timeout 900, but script run failed in 45s

[zerosnacks]

Hi @Aliceonly

What blockchain are you targeting? Are the RPCs you are using protected by an API key or are they public? Does it consistently fail on that specific transaction, around the same time or at around a specific transaction count?

[Aliceonly]

Hi @Aliceonly

What blockchain are you targeting? Are the RPCs you are using protected by an API key or are they public? Does it consistently fail on that specific transaction, around the same time or at around a specific transaction count?

Thx for reply, I target Berachain bArtio, it mostly fail on broadcasting batch txs in one script. Also, I tried diff rpcs in private(like quicknode) and public, same situation. It may be that the state of this blockchain is not synchronised in a timely manner or rpc not stable causing the rpc return null of tx receipt tentatively, but it will fails all the script, esp in github action it's fatal

[grandizzy]

I see a similar failure in https://github.com/foundry-rs/foundry/actions/runs/12664378135/job/35292428706#step:12:283 but it's passing on next attempt, cannot reproduce locally either...

Maybe we should not exit on first failure here but retry couple of times as the receipt could not be available right away?

foundry/crates/script/src/progress.rs

Lines 213 to 217 in ad09bbe

	Err(err) => {
	errors.push(format!("Failure on receiving a receipt for {tx_hash:?}:\n{err}"));
	seq_progress.inner.write().finish_tx_spinner(tx_hash);
	}

Le: probably this started to manifest more from when introducing better error handling (previously script was just hanging waiting for receipt if error) d402afd#diff-40b142bf1cc0e034c56533fad30c71161b2cc0b4dd4d6a72468e0649e3c7002dR52

[Aliceonly]

I see a similar failure in https://github.com/foundry-rs/foundry/actions/runs/12664378135/job/35292428706#step:12:283 but it's passing on next attempt, cannot reproduce locally either...

Maybe we should not exit on first failure here but retry couple of times as the receipt could not be available right away?

foundry/crates/script/src/progress.rs

Lines 213 to 217 in ad09bbe

Err(err) => {
errors.push(format!("Failure on receiving a receipt for {tx_hash:?}:\n{err}"));

 seq_progress.inner.write().finish_tx_spinner(tx_hash); 

}

Agree, it will happen more frequently on online chain cuz many rpc and testnet are not stable. It fails whole broadcast prograss, esp in workflow that's annoying

[klkvr]

for context: this error is most likely coming from here https://github.com/alloy-rs/alloy/blob/b9b2da02bfac649bd06b30bd970ea63470a23d70/crates/provider/src/heart.rs#L238

which means that transaction was included into latest block but receipt for it is still not available