Skip to content
This repository has been archived by the owner on Jul 13, 2022. It is now read-only.

duplicate txn error does not consider step being moved #54

Open
dbeal-eth opened this issue Jul 7, 2022 · 0 comments
Open

duplicate txn error does not consider step being moved #54

dbeal-eth opened this issue Jul 7, 2022 · 0 comments

Comments

@dbeal-eth
Copy link
Collaborator

suppose you have cannonfile like

[invoke.one]
step =1
[invoke.two]
step = 2

and change it to

[invoke.one]
step = 2
[invoke.two]
step = 2

if you have already built it, you will get an error that the txn has already been run. but in reality, the txn has been removed from a previous step and moved to a new step.

this will likely be fixed by topological cannonfiles.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant