search

trufflesuite / truffle

:warning: The Truffle Suite is being sunset. For information on ongoing support, migration options and FAQs, visit the Consensys blog. Thank you for all the support over the years.
https://consensys.io/blog/consensys-announces-the-sunset-of-truffle-and-ganache-and-new-hardhat?utm_source=github&utm_medium=referral&utm_campaign=2023_Sep_truffle-sunset-2023_announcement_
MIT License
14.02k stars 2.32k forks source link

nonce-like issues with Tezos contract? #2801

Open tcoulter opened 4 years ago

tcoulter commented 4 years ago

In the alphaTez branch, in a console, I pressed Ctrl+C while a call to a contract function was executing. I forgot to add await, so I "quit it" to send the request again.

On the second request, I got an error from the blockchain node suggesting it expected 962, but got 961. I tried the request again, and it failed in the same way. Eventually the transaction succeeded. This suggests a nonce-like state issue recorded in truffle-contract somewhere, much like we had in the past with Ethereum, that eventually fixes itself due to what I'd guess is some state check finally succeeding (totally guessing here). Is this helpful?

Steps to reproduce:

  1. In the console, call some function on a Tezos contract abstraction, like instance.main(3), preferably against a really slow testnet.
  2. After a second or two, press Ctrl-C.
  3. Try calling the function on the abstraction again. It should fail like the image below.
  4. Wait a while, or keep trying. It'll eventually succeed.

image

CruzMolina commented 4 years ago

Unfortunately this appears to be a known issue with the current implementation of Tezos.

See ecadlabs/taquito#213, https://gitlab.com/tezos/tezos/issues/644, & https://gitlab.com/tezos/tezos/issues/36.

dvkam commented 2 years ago

The issue 644 is at least fixed now

BearCooder commented 1 year ago

Hello @haltman-at & @fainashalts can you please make a statement as to why Tezos support is not a priority anymore? To be honest it leaves a bad taste after the big announcement od Tezos support in Truffle (Twitter and Blogpost) over two years ago. The funny thing is the support didnt last long, less than a year later Truffle started to ghost all issues and update requests on github or stated to do it later.. why the sudden change back then?

At least make either make it official and announce that you are not supporting Tezos anymore or at least update Tezos Truffle to current protocol standard. I dont know maybe its a failure on the communication side, maybe Truffle @tcoulter and Tezos Foundation @drchrispinnock need to talk but the current state is unfortunate.