feat(cheatcodes): add --fork-retry + --fork-retry-backoff equivalent to vm.create*Fork

[anajuliabit]

Component

Forge

Describe the feature you would like

Most of our integration tests are multichain, meaning we use vm.createFork to set up the forks. We can't use the --fork-url option because we want to ensure that the fork IDs have the same order, regardless of which chain the tests belong to.

For example, we always instantiate the forks in the following order:

• ID 0: Moonbeam fork
• ID 1: Base fork
• ID 2: Optimism fork

When running a Base integration test, the setUp function first fetches the Moonbeam governor and executes any live proposals (that can be cross-chain).

This is why we cannot use --fork-url with forge test.

Please allow the --fork-retry and --fork-retry-backoff flags to be used without requiring the --fork-url.

Additional context

No response

[zerosnacks]

Hi @anajuliabit thanks for your suggestion,

Supportive of the idea, wondering how we can best implement this.
At the moment it doesn't seem like simply allowing --fork-retry / --fork-retry-backoff to be ran without --fork-url would have any effect as the two flows are quite distinct.

We could overload the vm.createFork / vm.createSelectFork cheatcode to pass in additional configuration. This would allow you to configure a per-fork retries and backoff which seems desirable.

[pheobeayo]

May I take this issue on?

[PedroRosalba]

Can I work on this, please?

[zerosnacks]

Can I work on this, please?

I appreciate your enthusiasm but please do not claim tickets you are not intending to work on

You are already assigned to #7248 (comment) and others

[kien6034]

@zerosnacks can i work on this? The #9201 is open, but i believe most of the works is done

[zerosnacks]

Thanks Kien, all good - assigned to you

[kien6034]

@zerosnacks sorry for taking this long, i forget that i'm assigned to this issue , i've been busy this month, never actually got the time to do this issue

i've just un-assign myself for others to take the issue