Has anyone seen an error like the following?
ERROR: <class 'pistonapi.exceptions.UnhandledRPCError'>::::4030100 transaction_expiration_exception: transaction expiration exception
I found the logic that raises this exception in https://github.com/steemit/steem/blob/master/libraries/chain/database.cpp and I'm just not sure what is causing my transaction to expire. Has anyone seen this before or know how to prevent a transaction from expiring? I'm just doing a simple vote via the Piston lib.
//Skip all manner of expiration and TaPoS checking if we're on block 1; It's impossible that the transaction is
//expired, and TaPoS makes no sense as no blocks exist.
if( BOOST_LIKELY(head_block_num() > 0) )
{
if( !(skip & skip_tapos_check) )
{
const auto& tapos_block_summary = get< block_summary_object >( trx.ref_block_num );
//Verify TaPoS block summary has correct ID prefix, and that this block's time is not past the expiration
STEEMIT_ASSERT( trx.ref_block_prefix == tapos_block_summary.block_id._hash[1], transaction_tapos_exception,
"", ("trx.ref_block_prefix", trx.ref_block_prefix)
("tapos_block_summary",tapos_block_summary.block_id._hash[1]));
}
fc::time_point_sec now = head_block_time();
STEEMIT_ASSERT( trx.expiration <= now + fc::seconds(STEEMIT_MAX_TIME_UNTIL_EXPIRATION),
transaction_expiration_exception,
"", ("trx.expiration",trx.expiration)("now",now)("max_til_exp",STEEMIT_MAX_TIME_UNTIL_EXPIRATION));
if( has_hardfork( STEEMIT_HARDFORK_0_9 ) ) // Simple solution to pending trx bug when now == trx.expiration
STEEMIT_ASSERT( now < trx.expiration, transaction_expiration_exception, "", ("now",now)("trx.exp",trx.expiration) );
STEEMIT_ASSERT( now <= trx.expiration, transaction_expiration_exception, "", ("now",now)("trx.exp",trx.expiration) );
}
@cmtzco so you are building another BOT ?
Nope, I'm improving the ones I have :) Nothing harmful. Always to help the minnows and newcomers.
Hey it seems to be working fine!
nice post... upvote done
I have no clue about tech talk or computers but good luck with what your doing if it helps the newbies and basic users like me
heyy thanks for stopping by on ma page. ive followed ya.
Lol,this kind of error is another thinooo
Congratulations @cmtzco! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOPgood job @cmtzco
How are your friends steemit hopefully still be given health. And I hope your days are fun, with your latest posts, which inspire and inspire many of Steemit's loyal readers.
you are a lot of your good posts This is a very interesting and useful post, so my heart's intention to read and see in detail the posts you share.
I voted and followed you.
Congratulations @cmtzco! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOP@cmtzco thanks you give me upvote
let me follow you.
Hello cmtzo! I just saw ur profile and I must say u have earned alot of dollars, reputation and followers in a very short time. I am so frustrated these days because I try to post my best content here on steemit.com and it does not reach out to enough people. can u please share ur strategy and also look at my profile, and tell me what improvements can I make inorder to gain more attention :)
Congratulations @cmtzco! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOPThis is likely the result of a bandwidth issue where too many transactions are getting committed to the block that you are trying to commit your transaction to. The blockchain will reject the block, which is where this error comes from. I believe this error is universal - if you are getting it so are other people trying to commit a transaction to this block. One way to handle this is to have an exception that catches this issue and retries at a later time. Eventually the node that is committing your transaction will commit it to a different block which will likely get accepted to the blockchain.