Eos: You can try embedding eosio nonce action inside your transaction to ensure uniqueness.

[lingyiliu016]

when I push action on twice, error occured!
details are as follows:
cleos push action child.acnt ercbalanceof '["child.acnt"]' -p child.acnt
Error 3040008: duplicate transaction
You can try embedding eosio nonce action inside your transaction to ensure uniqueness.
Error Details:
duplicate transaction 798086f342c8261ff0324253a6b5362f7cfb64f4280e9aea5e8d017581fb538b
what should I do? How can I embedding eosio nonce action inside my transaction?
give me some suggesstion,please!

[maxb14]

Just add -f option like that :

cleos push action child.acnt ercbalanceof '["child.acnt"]' -p child.acnt -f

[moskvanaft]

@lingyiliu016 "duplicate transaction" maybe a sign of another problem - your nodeos is not producing blocks.
Otherwise transactions submitted even with 1 second interval should be unique since they reference different head blocks (even if all other fields in the transactions are exactly the same). In your case head block seem to be not advancing.

Meanwhile I am closing this ticket - there is no issue with EOS software and there is no information to say what was wrong with nodeos (most likely block production was not enabled).

[ekkis]

1 second is a long time if your running a test suite where calls take fractions of a second. I'm having the same issue but using eosjs, which I don't believe supports an equivalent of --force-unique. any recommendations?

[heifner]

You can add an attribute to your action and send a random number or incrementing number. Or add a memo field and add unique strings.

[ekkis]

I had tried sending a random number in the memo field but it didn't work. I also read in other posts about the inclusion of a "nonce" though I find no authoritative documentation on how that might be done

[heifner]

Here is how nonce is done in cleos

chain::action generate_nonce_action() {
   return chain::action( {}, config::null_account_name, name("nonce"), fc::raw::pack(fc::time_point::now().time_since_epoch().count()));
}

[ekkis]

in my case the transaction is composed in eosjs. I'm not yet familiar with creating transactions from c++

in fact, what's odd is that if I change the amount I'm transferring it solves the problem, but adding a memo field with a random number doesn't

[heifner]

Sorry, I'm not familiar with eosjs. Maybe ask there. A random number on memo should work just fine.

[bakasura980]

@ekkis, Check eoslime, the JS framework supports it