search

hirosystems / clarinet

Write, test and deploy high-quality smart contracts to the Stacks blockchain and Bitcoin.
https://hiro.so/clarinet
GNU General Public License v3.0
307 stars 141 forks source link

Deployment plan conflicts #1579

Open whoabuddy opened 1 month ago

whoabuddy commented 1 month ago

Describe the bug

When I run clarinet check I'm prompted to overwrite the deployment plan for simnet.

When I run npm run test on my contracts, the deployment plan is updated again in a different format.

To Reproduce

Steps to reproduce the behavior:

  1. Create a new clarinet project and contract
  2. Run clarinet check for the project
  3. Run npm run test for the project
  4. See updated deployment plan

Expected behavior

The deployment plan should be consistent between both tools.

Screenshots

After running the tests:

image

Changes requested by clarinet check:

image

Environment (please complete the following information):

hugocaillard commented 1 month ago

Related to https://github.com/hirosystems/clarinet/issues/1368 Also there could be some quick win there, the new deployment plan strategy shouldn't save empty batches (with: transactions: []) Will take a look, thanks for reporting @whoabuddy