search

tokenika / eosfactory

Python-based EOS smart-contract development & testing framework
http://eosfactory.io/
Other
243 stars 62 forks source link

Should force unique be set by default? #139

Closed ryanleecode closed 5 years ago

ryanleecode commented 5 years ago

Wondering whats everyone's thoughts on the force unique flag being set on by default? Often times I find myself recreating the same account and pushing the same action in the setup phase but I run into this error when doing so

Error 3040008: Duplicate transaction
You can try embedding eosio nonce action inside your transaction to ensure uniqueness.
Error Details:
duplicate transaction accf37ffb1beeea853031c6ad8a74426cc4ca3f76604f95450eb60976fccab1d

Obviously this is fixed by adding the force unique flag to each push action call... however it would seem more convenient if it was on by default in the context of writing tests.

stefanzarembinski commented 5 years ago

I know this error: it happens bay it disappears in a subsequent execution of the same command. I believe that it proves an instability problem of the blockchain.

The blockchain features few instability problems. For example, is refuses restarting sometimes. EOSFactory meets this problem with sequential attempts. In the same way another instability is addressed. I plan to include the Duplicate transaction error to the same service.

stefanzarembinski commented 5 years ago

It is finished, I see. Closing.