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

‘cleos get transaction_id ’ tests different data, always returning the same id. #7816

Closed
cppfuns opened this issue Aug 28, 2019 · 0 comments

Comments

@cppfuns
Copy link

commented Aug 28, 2019

Due to some problems, (guessing that a single nodeos pushed too many transactions) caused the transaction push to return timeout, but in fact the transaction has been pushed successfully. The solution I think of temporarily is that I hope to calculate the ID of the transaction in advance before the transaction is submitted, so that when the transaction is repeated, it is first determined whether the transaction ID already exists. After searching, I found that 'cleos get transaction_id ' (#6830) seems to be the function I want, but testing different data, always returning the same id. I use the method problem? Or is this feature not used like this?

cleos get transaction_id 1e24d670f7c504c63184cc4be449f19685a2215f95d03aba7d61f4aac3c77eb8.json
374708fff7719dd5979ec875d56cd2286f6d3cf7ec317a3b25632aab28ec37bb
cleos get transaction_id 53a7af39b92fc811b7ccae2e3602964fd21263162756f491cb875e80b5e7a886.json
374708fff7719dd5979ec875d56cd2286f6d3cf7ec317a3b25632aab28ec37bb

1e24d670f7c504c63184cc4be449f19685a2215f95d03aba7d61f4aac3c77eb8.zip
53a7af39b92fc811b7ccae2e3602964fd21263162756f491cb875e80b5e7a886.zip

@cppfuns cppfuns closed this Aug 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.