[OP Stack Deployment] No matching artifact found

[yiming-face]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

after run
forge script scripts/Deploy.s.sol:Deploy --sig 'sync()' --rpc-url $L1_RPC_UR
get this error
"No matching artifact found"

at the second sync call: Syncing deployment DisputeGameFactory: contract DisputeGameFactory.0.8.15

foundry tries to call function sync, which is looking for contract DisputeGameFactory.0.8.15 , but this is clearly not a correct contract name

and in my forge-artifacts directory, under DisputeGameFactory.sol, there are two json files:
DisputeGameFactory.0.8.15.json
DisputeGameFactory.0.8.19.json

I think this may affect the "sync" call,

does anyone get the same issue?

Logs

Connected to network with chainid 11155111
Storing temp deployment data in /home/ubuntu/op-stack/optimism/packages/contracts-bedrock/deployments/getting-started/.deploy
DeployConfig: reading file /home/ubuntu/op-stack/optimism/packages/contracts-bedrock/deploy-config/getting-started.json
Deploying from Deploy
Deployment context: getting-started
Syncing 27 deployments
Using deployment artifact /home/ubuntu/op-stack/optimism/packages/contracts-bedrock/broadcast/Deploy.s.sol/11155111/run-latest.json
Syncing deployment AddressManager: contract AddressManager
Syncing deployment DisputeGameFactory: contract DisputeGameFactory.0.8.15

Additional Information

No response

Feedback

No response

[Chomtana]

Hi, please deploy contracts from op-contracts/v1.3.0 branch and switch back to v1.7.2 branch for running op-node, op-batcher, and op-proposer

cd optimism
git checkout op-contracts/v1.3.0

... Deploy contract and init genesis commands ...

git checkout v1.7.2

... Start OP Stack chain commands ...

Sorry for misleading docs.

[hardXcoder]

I change the visibility of the functions in the contracts mentioned in the error. Removed the "view" modifier, then it compiles. Is it the right way ?

[yiming-face]

I have the same err as @hardXcoder after switch to branch op-contracts/v1.3.0

and here is my foundryup print out...

foundryup: installed - forge 0.2.0 (72bc4f4 2024-04-08T00:16:33.234657619Z)
foundryup: installed - cast 0.2.0 (72bc4f4 2024-04-08T00:16:33.255574701Z)
foundryup: installed - anvil 0.2.0 (72bc4f4 2024-04-08T00:16:33.272515490Z)
foundryup: installed - chisel 0.2.0 (72bc4f4 2024-04-08T00:16:33.271907196Z)
foundryup: done!

[yiming-face]

hi, @hardXcoder , after you changed visibility, does the following steps work well?

[rabbitprincess]

It still fail after switch to op-contracts/v1.3.0. cause of failure seems to be latest release of foundry.
set specific version when install foundry. below is example
https://github.com/gokch/optimism_builder/blob/main/init/Dockerfile#L21

[Chomtana]

Let's use the branch tutorials/chain as pointed out in the Dockerfile you have sent. Thank you @gokch