BTSX 0.4.12 Released - Mandatory Upgrade by Sept. 5 19:00 UTC

[maqifrnswa]

Are you building in RELEASE mode?

I didn't specify either, the full build log is here:
https://launchpadlibrarian.net/184045129/buildlog_ubuntu-trusty-amd64.bitsharesx_0.4.12-0ubuntu1~ppa2_UPLOADING.txt.gz

I don't see DEBUG anywhere in the build log.

[huzhuzhu]

following are the cmd that i used to build v0.4.12

git clone https://github.com/dacsunlimited/bitsharesx.git
cd bitsharesx
git checkout 0.4.12
git submodule init
git submodule update
cmake .
make
*

getting following error while indexing .

have to remove the old blockchain and re-download

Code: [Select]


Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Re-indexing database... Approximately 0.00% complete.------------ error --------------
10 assert_exception: Assert Exception
delegate_record.valid():
    {}
    th_a  chain_database.cpp:1219 get_slot_signee

    {"timestamp":"20140719T031850","ordered_delegates":[10206,10243,14758,14020,14025,18764,10207,18766,18771,10214,14764,10213,8790,10323,14759,2151,14757,266,334,6939,2156,10173,9879,10287,1193,9870,8679,10171,10288,338,335,6006,136,10174,6212,875,319,9811,8792,307,10274,774,371,9882,3324,317,9880,9878,884,10082,10879,318,306,15017,169,5722,5503,337,9875,10083,2158,10093,10264,669,10155,13718,89,1034,9871,299,3649,56,5589,14872,21537,10,66,59,1,16503,10493,10810,54,10086,12313,71,13719,21539,376,10488,23569,10510,6,12316,12314,21130,22918,22920,10487,6582,22353]}
    th_a  chain_database.cpp:1222 get_slot_signee

    {"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:884 extend_chain

    {"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:1423 push_block

    {"data_dir":"/home/ubuntu/.BitSharesX/chain"}
    th_a  chain_database.cpp:1145 open

    {"data_dir":"/home/ubuntu/.BitSharesX"}
    th_a  client.cpp:1692 open


that's the same error I got, after that I deleted the chain and restarted. When I git the same block I got:

Code: [Select]

bitshares_client: /build/buildd/bitsharesx-0.4.12/libraries/fc/include/fc/optional.hpp:197: T* fc::optional<T>::operator->() [with T = bts::blockchain::market_order]: Assertion `_valid' failed.
I seem to get it from the PPA build but not from my own github pull. They are identical, so I don't know what's happening there

Are you building in RELEASE mode?

[bytemaster]

getting following error while indexing .

have to remove the old blockchain and re-download

Code: [Select]


Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Re-indexing database... Approximately 0.00% complete.------------ error --------------
10 assert_exception: Assert Exception
delegate_record.valid():
    {}
    th_a  chain_database.cpp:1219 get_slot_signee

    {"timestamp":"20140719T031850","ordered_delegates":[10206,10243,14758,14020,14025,18764,10207,18766,18771,10214,14764,10213,8790,10323,14759,2151,14757,266,334,6939,2156,10173,9879,10287,1193,9870,8679,10171,10288,338,335,6006,136,10174,6212,875,319,9811,8792,307,10274,774,371,9882,3324,317,9880,9878,884,10082,10879,318,306,15017,169,5722,5503,337,9875,10083,2158,10093,10264,669,10155,13718,89,1034,9871,299,3649,56,5589,14872,21537,10,66,59,1,16503,10493,10810,54,10086,12313,71,13719,21539,376,10488,23569,10510,6,12316,12314,21130,22918,22920,10487,6582,22353]}
    th_a  chain_database.cpp:1222 get_slot_signee

    {"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:884 extend_chain

    {"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:1423 push_block

    {"data_dir":"/home/ubuntu/.BitSharesX/chain"}
    th_a  chain_database.cpp:1145 open

    {"data_dir":"/home/ubuntu/.BitSharesX"}
    th_a  client.cpp:1692 open


that's the same error I got, after that I deleted the chain and restarted. When I git the same block I got:

Code: [Select]

bitshares_client: /build/buildd/bitsharesx-0.4.12/libraries/fc/include/fc/optional.hpp:197: T* fc::optional<T>::operator->() [with T = bts::blockchain::market_order]: Assertion `_valid' failed.
I seem to get it from the PPA build but not from my own github pull. They are identical, so I don't know what's happening there

Are you building in RELEASE mode?

[maqifrnswa]

getting following error while indexing .

have to remove the old blockchain and re-download

Code: [Select]


Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Re-indexing database... Approximately 0.00% complete.------------ error --------------
10 assert_exception: Assert Exception
delegate_record.valid():
    {}
    th_a  chain_database.cpp:1219 get_slot_signee

    {"timestamp":"20140719T031850","ordered_delegates":[10206,10243,14758,14020,14025,18764,10207,18766,18771,10214,14764,10213,8790,10323,14759,2151,14757,266,334,6939,2156,10173,9879,10287,1193,9870,8679,10171,10288,338,335,6006,136,10174,6212,875,319,9811,8792,307,10274,774,371,9882,3324,317,9880,9878,884,10082,10879,318,306,15017,169,5722,5503,337,9875,10083,2158,10093,10264,669,10155,13718,89,1034,9871,299,3649,56,5589,14872,21537,10,66,59,1,16503,10493,10810,54,10086,12313,71,13719,21539,376,10488,23569,10510,6,12316,12314,21130,22918,22920,10487,6582,22353]}
    th_a  chain_database.cpp:1222 get_slot_signee

    {"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:884 extend_chain

    {"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:1423 push_block

    {"data_dir":"/home/ubuntu/.BitSharesX/chain"}
    th_a  chain_database.cpp:1145 open

    {"data_dir":"/home/ubuntu/.BitSharesX"}
    th_a  client.cpp:1692 open


that's the same error I got, after that I deleted the chain and restarted. When I git the same block I got:

Code: [Select]

bitshares_client: /build/buildd/bitsharesx-0.4.12/libraries/fc/include/fc/optional.hpp:197: T* fc::optional<T>::operator->() [with T = bts::blockchain::market_order]: Assertion `_valid' failed.
I seem to get it from the PPA build but not from my own github pull. They are identical, so I don't know what's happening there

[xeroc]

Gave you a thumbs up.  Will vote for you next time I vote.

could you also consider
https://bitsharestalk.org/index.php?topic=7673.0
a.delegate.xeroc
b.delegate.xeroc
next time your vote ..

you can keep delegate.xeroc up and running .. if possible ..

6 delegates is just a little too much responsibility for my one-man-show IMHO :-)

[huzhuzhu]

getting following error while indexing .

have to remove the old blockchain and re-download

Code: [Select]


Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Re-indexing database... Approximately 0.00% complete.------------ error --------------
10 assert_exception: Assert Exception
delegate_record.valid():
    {}
    th_a  chain_database.cpp:1219 get_slot_signee

    {"timestamp":"20140719T031850","ordered_delegates":[10206,10243,14758,14020,14025,18764,10207,18766,18771,10214,14764,10213,8790,10323,14759,2151,14757,266,334,6939,2156,10173,9879,10287,1193,9870,8679,10171,10288,338,335,6006,136,10174,6212,875,319,9811,8792,307,10274,774,371,9882,3324,317,9880,9878,884,10082,10879,318,306,15017,169,5722,5503,337,9875,10083,2158,10093,10264,669,10155,13718,89,1034,9871,299,3649,56,5589,14872,21537,10,66,59,1,16503,10493,10810,54,10086,12313,71,13719,21539,376,10488,23569,10510,6,12316,12314,21130,22918,22920,10487,6582,22353]}
    th_a  chain_database.cpp:1222 get_slot_signee

    {"block":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:884 extend_chain

    {"block_data":{"previous":"0000000000000000000000000000000000000000","block_num":1,"timestamp":"20140719T031850","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"38c370dbf65ab46b5a403dd3d44729bceeb282cb","previous_secret":"9c9dc7b87c243311961ac3e8000b5827841372b4","delegate_signature":"20248c112ed3b1c56696cae6e0b8ff55a0403eb0287b445813a99262e141f7cd56e7004948cf962bd76a9649fe749d14a6b88b5a700e11e1b068042d0972f45396","user_transactions":[]}}
    th_a  chain_database.cpp:1423 push_block

    {"data_dir":"/home/ubuntu/.BitSharesX/chain"}
    th_a  chain_database.cpp:1145 open

    {"data_dir":"/home/ubuntu/.BitSharesX"}
    th_a  client.cpp:1692 open


[emski]

Is blockchain rescan in another thread?

Is there a way to stop blockchain rescan once it started? ( I tried wallet_set_transaction_scanning false - Didn't work)

UPDATE: I'm not missing blocks while delegate's wallet is rescanning blockchain even though I have 30+ accounts in the wallet.

[emski]

Updated:
angel.bitdelegate
immortal.bitdelegate (I'll describe it soon but the intended purpose of all income is to support the network - seed node(s), delegate backups, etc)

[bytemaster]

delegate.webber updated to 0.4.12,please vote me back

Gave you a thumbs up.  Will vote for you next time I vote.

[yinchanggong]

google.helloworld 99.96%, microsoft.helloworld 99.4%  updated to 0.4.12. Thanks.

[Webber]

delegate.webber updated to 0.4.12,please vote me back

[bytemaster]

I keep crashing on one my my machines while syncing with the chain at some block 16 days ago:
bitshares_client: /build/buildd/bitsharesx-0.4.12/libraries/fc/include/fc/optional.hpp:197: T* fc::optional<T>::operator->() [with T = bts::blockchain::market_order]: Assertion `_valid' failed.

sorry for not enough detail, I'm still debugging

Make sure you build in RELEASE mode.   It is known not to work in DEBUG mode.   The fix for DEBUG mode is implemented but didn't make it into 0.4.12.

[maqifrnswa]

I keep crashing on one my my machines while syncing with the chain at some block 16 days ago:
bitshares_client: /build/buildd/bitsharesx-0.4.12/libraries/fc/include/fc/optional.hpp:197: T* fc::optional<T>::operator->() [with T = bts::blockchain::market_order]: Assertion `_valid' failed.

sorry for not enough detail, I'm still debugging

[xeroc]

Downgrade GCC... 4.8 seems to work.  4.9 seems like it may be too new/buggy.

neh .. that is not so easy with a rolling-release based distribution ...

gonna keep the delegates on 0.4.11 until tomorrow and try to figure out how to fix it until the hardfork .. worst case scenario .. delegates have to run on the backup machine

[bytemaster]

I am getting more and more used to theses updates for the delegates ... second time in a row I havent missed a single block during update .. yeehha

Now that stability has been mostly addressed, we are going to aim for weekly sprints with new features and bug fixes.   We will also be making some "donations" to the delegates to compensate them for the added work they are doing by updating on such a frequent basis.

Please consider what we said the last days about paying "standby delegates"...(at least the top stand-by delegates)
I am sure many of them update their clients regular so they are ready in case they are voted in... It's unfair for them because they are "working" without any payment at all compared with the active one.
Imagine some "hard work" delegates  that are on spots 90-101 and they are standby delegates every now and then... It's an ugly experience!


PS Consider to donate more to low pay-rate delegates. They needed more.

I'll consider that as well.