Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignition status command does not work with external artifacts deployed #797

Open
sim31 opened this issue Aug 22, 2024 · 1 comment
Open
Assignees
Labels
status:ready This issue is ready to be worked on type:bug Something isn't working

Comments

@sim31
Copy link

sim31 commented Aug 22, 2024

Version of Hardhat

2.22.8

What happened?

Same setup as in NomicFoundation/hardhat#5659. I'm using ignition to deploy external artifacts.

After successful deployment I ran npx hardhat ignition status op-sepolia-1 I received this output:

Error HH700: Artifact for contract "Orec" not found. 

For more info go to https://hardhat.org/HH700 or run Hardhat with --show-stack-traces

If I run the deploy command again it says `Nothing new to deploy based on previous execution stored in ./ignition/deployments/op-sepolia-1" (as expected) so it seems that deploy command finds the required artifacts but status command does not?

Expected status command to print addresses of deployed contracts.

Minimal reproduction steps

  1. Create sample hardhat project 1, compile it;
  2. Create hardhat project 2, create ignition module that tries to deploy artifact from project 1 (as described here);
  3. Use ignition to deploy to testnet (I was deploying to OP Sepolia)
  4. Try ignition status <deployment-id> command

Search terms

ignition

@kanej kanej assigned kanej and unassigned ChristopherDedominici Aug 23, 2024
@kanej kanej added type:bug Something isn't working status:ready This issue is ready to be worked on and removed status:triaging labels Aug 23, 2024
@kanej kanej transferred this issue from NomicFoundation/hardhat Aug 23, 2024
@kanej
Copy link
Member

kanej commented Aug 23, 2024

While #5659 is a limitation (we don't have all the info needed for verification), this looks like a bug where we are making incorrect assumptions in the status command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:ready This issue is ready to be worked on type:bug Something isn't working
Projects
Status: To-do
Status: Todo
Development

No branches or pull requests

3 participants