Quote from: bdnoble on August 22, 2014, 12:39:03 pm

Anyone else seeing this message? Is this bad? 

Code: [Select]

nobledelegate (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
unable to find key 0
    {"key":0}
    th_a  level_map.hpp:91 fetch
error fetching key 0
    {"key":0}
    th_a  level_map.hpp:101 fetch

    {"block_num":0}
    th_a  chain_database.cpp:1256 get_block_id

    {"block_num":0}
    th_a  chain_database.cpp:1241 get_block_header

    {}
    th_a  common_api_client.cpp:1859 get_info

    {"command":"get_info"}
    th_a  cli.cpp:471 execute_command
nobledelegate (unlocked) >>>


I have filed a bug report on this. https://github.com/BitShares/bitshares_toolkit/issues/669   

Probably harmless... let me know if you are able to sync

Quote

I guess this is because you have produced the block in this round, and there will be a shuffle before you produce next block, so the program can not calculate exactly time when you will produce your next block

This is not how it works... you can produce multiple blocks in a single round if someone misses.  So that is not why it is NULL.

That said, I think this thread should be updated to reflect that delegates should not upgrade unless they want to help test and are prepared to upgrade one more time before wednesday.   Delegates that want to be lazy and upgrade only once should not try this release.

After discussions going on I have tweaked the bitasset FDIC system so the hardfork will be slightly different than we see in this release.  In fact, we may want to push the hard-fork back a few days so that all the issues can be worked out.