BitShares Forum
Main => General Discussion => Topic started by: bytemaster on September 04, 2014, 07:03:47 pm
-
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.12
Delegates & Seed Nodes should upgrade ASAP.
Publish your version info as "0.4.12" after you upgrade to keep my vote.
-
riverhead-del-server-1 and chain/seed nodes updated to 0.4.12.
Note to other delegates: It takes longer than previous versions to re-index the database. Make sure you give yourself enough time or start 0.4.12 in it's own data-dir.
I like the improvements to the CLI :)
-
I like the improvements to the CLI :)
Which ones?
-
Done.
delegate1-galt
delegate1.john-galt
Upgraded to 0.4.12
-
I like the improvements to the CLI :)
Which ones?
The formatted feedback after updating my public_data vs the JSON dump.
-
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.12
Delegates & Seed Nodes should upgrade ASAP.
Publish your version info as "0.4.12" after you upgrade to keep my vote.
Is there no OSX version? Do not see it on Github. Only see Windows version.
-
I like the improvements to the CLI :)
Which ones?
kokojie updated to 0.4.12
I like how to re-indexing in CLI is showing an actual percentage now.
-
Updated doxymoron-delegate.
-
So the blockchain is already about 386MB and we're just getting started. Most financial institutions are required to keep records for five years. Is there any plan to prune the blockchain or address this side effect of 10 second blocks?
-
So the blockchain is already about 386MB and we're just getting started. Most financial institutions are required to keep records for five years. Is there any plan to prune the blockchain or address this side effect of 10 second blocks?
The raw chain (just blocks and transactions) is 88 MB
The index used to maintain quick access / sort /etc is 277 MB
Future plans call for removing the TITAN information (encrypted data) from the blockchain and relying on a notification service. This should reduce transaction sizes by up to 50%
The next release will also support paying transaction fees in USD as well as bids with USD/CNY/etc. This should reduce the number of signatures per transaction.
Reducing the size of the "raw chain" is easy, reducing the size of the index on that chain is much harder.
-
With the Windows Binary on my Win7 machine the splash screen disappeared shortly after the re-index started. The "Setup" task bar item is still there and the harddrive is churning away (BitSharesX32.exe is taking up about 280MB of ram).
I'll update if it comes back after indexing.
-
Delegates, seed node and website client updated.
-
With the Windows Binary on my Win7 machine the splash screen disappeared shortly after the re-index started. The "Setup" task bar item is still there and the harddrive is churning away (BitSharesX32.exe is taking up about 280MB of ram).
I'll update if it comes back after indexing.
I bet it will try to take just about 1000MB
-
calabiyau
neuronics
Upgraded to 0.4.12
Percentage on reindexing - nice :)
-
*.delegate.xeroc
*.delegate.charity
are compiling! upgrade to be announced in the data field
-
btsx.chinesecommunity
bts.xiaoshan
upgraded to 0.4.12 . Version published also. +5%
-
delegate*.xeldal updated 0.4.12
data field updated
auto feeds updated
-
spartako,spartako1,spartako2 active delegates upgraded to 0.4.12
data field updated to {"version": "0.4.12"}
btsx_feed_auto.py USD BTC CNY (with 1% update: 'if fabs(change) > 1' )
-
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 :)
-
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.
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
seems like I need to run my delegate on the (debian) backup server until this is resolved ... no idea what to do though :(
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
I got that error before in earlier versions, I had to delete the whole directory and use "git clone", instead of "git pull" to resolve it.
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
Upgrade GCC and make sure you have plenty of ram.
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
Upgrade GCC and make sure you have plenty of ram.
gcc 4.9.1 ... 6 GB RAM .. seems to be a distribution-related issue :(
-
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.
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
Upgrade GCC and make sure you have plenty of ram.
gcc 4.9.1 ... 6 GB RAM .. seems to be a distribution-related issue :(
Downgrade GCC... 4.8 seems to work. 4.9 seems like it may be too new/buggy.
-
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.
-
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 :)
-
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
-
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.
-
delegate.webber updated to 0.4.12,please vote me back
-
google.helloworld 99.96%, microsoft.helloworld 99.4% updated to 0.4.12. Thanks.
-
delegate.webber updated to 0.4.12,please vote me back
Gave you a thumbs up. Will vote for you next time I vote.
-
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)
-
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.
-
getting following error while indexing .
have to remove the old blockchain and re-download
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
-
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 :-)
-
getting following error while indexing .
have to remove the old blockchain and re-download
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:
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
-
getting following error while indexing .
have to remove the old blockchain and re-download
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:
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?
-
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
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:
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?
-
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.
-
getting following error while indexing .
have to remove the old blockchain and re-download
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
are you on 64bit (amd64) maybe? My 32 bit machines seem fine but 64 seem to have a problem. could just be a coincidence.
-
Immediately crashing on OSX 10.9.4
Getting error: "An error occurred while trying to start"
-
delegate.webber updated to 0.4.12,please vote me back
Gave you a thumbs up. Will vote for you next time I vote.
(http://allthingsd.com/files/2012/07/Commodus_thumbs_up.jpg)
-
(http://robohash.org/set_1/delegate.liondani?size=75x75)delegate.liondani successful upgraded to 0.4.12
-
e.coin/ bts.coin /bimin.coin are on V0.4.12
-
Immediately crashing on OSX 10.9.4
Getting error: "An error occurred while trying to start"
I'm also having problems with OSX 10.9.4..... I have missing balances. Tried using my backup JSON file, but still have the missing balances. Tried reindexing, no luck.
OK, I forgot that it takes about 30min to sink with the block chain. After sync my balances are just find. Then I imported my latest JSON file to get back my send to/from descriptions.
All working fine now.
-
Delegate alecmenconi updated to 0.4.12 now.
-
Immediately crashing on OSX 10.9.4
Getting error: "An error occurred while trying to start"
The fix is to delete /Library/Internet Plug-Ins/adobeaamdetect.plugin as it interferes with the client.
-
* bts500 are being upgraded.
Upgraded.
Version info published.
-
x.ebit, rose.ebit updated to 0.4.12 successfully +5%
Love BitRose~
-
done
btw, the 0.4.12 version consumes too much RAM. about 1.5G
-
updating
completed
running steadly
version info updated
Please vote me up
-
Done
-
dc-delegate
bitsharesx-delegate
updated to 0.4.12, and updated version info.
-
delegate.bitder updated to 0.4.12 and updated version info.
-
I suggest delegate to update the automatic feed price scripts.
the main different is use the median price to replace the average price.
you can change the pararm "median_length" to adjust the price change latency.
because version 0.4.12 will use feed price to decide the min cover price,
we need to protect the cover order from a serial margin call,
maybe cause of a suddenly price drop with a short period at the central trade site.
my English is poor, maybe not say it clearly ???
updated:
1. update config file
2. use median price to replace average price, to protect system from a suddenly drop price with a short period at the central trade site.
-
I have win7x32, I downloaded the exe 0.4.12 in bitshare-x.info and it won't open the installation file, I think the exe file is winx64 because size is 33mb. I checked the github releases and downloaded the x32 there.
There should be x64 and x32 download files in bitshare-x.info
-
delegate.taolje
updated 0.4.12 and the automatic feed price scripts.
Good job, +5% +5% +5%
-
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.12
Delegates & Seed Nodes should upgrade ASAP.
Publish your version info as "0.4.12" after you upgrade to keep my vote.
I think we need checksum of every release, that we can make sure our download is correct.
-
*.chinese @ v0.4.12
-
Delegates:
www.minebitshares-com
www2.minebitshares-com
and seed nodes:
euseednode.minebitshares.com 54.77.51.177
auseednode.minebitshares.com 54.79.27.224
Updated to 0.4.12
The % progress display when re-indexing the database on startup is very useful...
btsx_feed_auto.py price feed scripts is also updated
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
Upgrade GCC and make sure you have plenty of ram.
gcc 4.9.1 ... 6 GB RAM .. seems to be a distribution-related issue :(
Downgrade GCC... 4.8 seems to work. 4.9 seems like it may be too new/buggy.
Just to say I confirm this bug as well. Running the latest Arch too.
EDIT: Pretty sure that there is a fix for this, just waiting upstream somewhere: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62079
-
Nice .. I found some fixes too from 2012 :)
Good to know i dont need to downgrade gcc ..
thx
-
sun.delegate.service
moon.delegate.service
@ v0.4.12
and public data update
{"version","0.4.12"}
-
Nice .. I found some fixes too from 2012 :)
Good to know i dont need to downgrade gcc ..
thx
Yeah, I just wonder when it'll make it into stable release...
-
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.
Emski just made me aware that I skrewed up again .. not missing a block but somehow managed to have both wallets unlocked for a longer time producing forks .. this enerves me a lot as I wrote scripts to prevent all of this
https://github.com/xeroc/pytshares/blob/master/enable-main.py
https://github.com/xeroc/pytshares/blob/master/enable-backup.py
I have no f**** clue how I skrewed it up this time ...
In a quick discussion with emski .. I desiced to shutdown the backup delegate completely and run only one delegate machine .. when doing updates I will probably miss some blocks .. but as we know .. missing blocks is not as bad as forks .. sorry for the invonvinience .. I learned my lesson
-
btw, the 0.4.12 version consumes too much RAM. about 1.5G
yeah, I initially thought that too, but then I checked and a good part of it was due to the reindexing, which is either leaking a bit or doesn't return the memory to the system immediately (this is an OS thing, the client can't do anything about it I believe). However, this only happens the first time you run the client when it needs to upgrade the db.
Shutting down the client and relaunching it "solved" it for me.
-
yes,i am also aware of this,the RAM usage drop down after server restart.
btw, the 0.4.12 version consumes too much RAM. about 1.5G
yeah, I initially thought that too, but then I checked and a good part of it was due to the reindexing, which is either leaking a bit or doesn't return the memory to the system immediately (this is an OS thing, the client can't do anything about it I believe). However, this only happens the first time you run the client when it needs to upgrade the db.
Shutting down the client and relaunching it "solved" it for me.
-
coolspeed
delegate.coolspeed
dac.coolspeed
updated to 0.4.12. Version published.
-
x64 wallet doesnt start instead shows an error message, please fix.
x86 wallet working fine!
-
I finally figured out why I was producing forks ... It was a cronjob that originally was used to overcome the crashing issues that unlocked the wallet ...
as the wallet is now much more stable I don't need that cronjob anylonger and hope to not skrew this up again .. sorry for that anyway
-
I'm also getting errors with this version, but i've not tried previous version on this computer. Anyone getting the same error?
(http://i.imgur.com/nTOQ1Vg.png)
-
The 64-bit .exe doesn't work. Have you tried the 32-bit one?
-
I'm also getting errors with this version, but i've not tried previous version on this computer. Anyone getting the same error?
(http://i.imgur.com/nTOQ1Vg.png)
Same here, ver. 0.4.12 from bitsharesx.info download is not even installing on a win7/64 machine. Previous versions installed - sometimes with a "little help". This should be fixed asap - frustrating experience for users downloading from the "official" site.
-
I got the same error when using the version you can download at http://bitshares-x.info/. The 32 bit version that worked for me can be downloaded here: https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.12/BitSharesX-0.4.12.exe
Perhaps somebody can fix the binary that is linked on http://bitshares-x.info?
-
Immediately crashing on OSX 10.9.4
Getting error: "An error occurred while trying to start"
You should check your default.log in ~/Library/Application Support/BitShares X/logs/default -- The real reason for that error should be shown there. Most likely you just need to delete ~/Library/Application Support/BitShares X/chain/index to force a rebuild of the index. PM me if you need any more help.
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
seems like I need to run my delegate on the (debian) backup server until this is resolved ... no idea what to do though :(
I got this error as well from a clean build. Building with clang works. If you like, I can give you a pkg.tar.xz. I'll also be updating my docker containers momentarily.
-
Hu ... on ArchLinux I am getting this internal compiler error:
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
} FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
seems like I need to run my delegate on the (debian) backup server until this is resolved ... no idea what to do though :(
I got this error as well from a clean build. Building with clang works. If you like, I can give you a pkg.tar.xz. I'll also be updating my docker containers momentarily.
I'd be interested to know how to compile with clang myself .. can you give a quick howto?
-
I'd be interested to know how to compile with clang myself .. can you give a quick howto?
It's really simple on Arch (but what isn't, really? :D). Just `pacman -Sy clang` and then `export CC=clang;export CXX=clang++` before running `make`.
-
I'd be interested to know how to compile with clang myself .. can you give a quick howto?
It's really simple on Arch (but what isn't, really? :D). Just `pacman -Sy clang` and then `export CC=clang;export CXX=clang++` before running `make`.
thought so .. trying now
i just wondered because my process list still states things from gcc while compiling ..
// edit: had to do a fresh checkout .. cmake somewhere stores the previous compiler :)
rm -rf CMakeFiles/ does the job too ...
thanks for the help
-
Oh, yeah you need to nuke the CMakeCache.txt file (or edit it manually and set the compilers).
-
I got the same error when using the version you can download at http://bitshares-x.info/. The 32 bit version that worked for me can be downloaded here: https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.12/BitSharesX-0.4.12.exe
Perhaps somebody can fix the binary that is linked on http://bitshares-x.info?
Working binaries - thank you. Only 26 MB versus 32.6 MB :o
-
I want to say that I am very impressed with how all of the delegates upgraded in a timely manner!
-
I'm also getting errors with this version, but i've not tried previous version on this computer. Anyone getting the same error?
(http://i.imgur.com/nTOQ1Vg.png)
Same here, ver. 0.4.12 from bitsharesx.info download is not even installing on a win7/64 machine. Previous versions installed - sometimes with a "little help". This should be fixed asap - frustrating experience for users downloading from the "official" site.
same problem here..
win 7 64Bit...
but 64 bit wallet do not work!!!
error msgbox on opening.
-
how much free ram to run wallet?
maybe this is the problem?
-
how much free ram to run wallet?
maybe this is the problem?
Right now on OS X it is using 1GB of ram.
-
how much free ram to run wallet?
maybe this is the problem?
Using ~ 1.4 GB on win7. Still "No connection" issues.
Try this: https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.12/BitSharesX-0.4.12.exe (https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.12/BitSharesX-0.4.12.exe)
-
I'd be interested to know how to compile with clang myself .. can you give a quick howto?
It's really simple on Arch (but what isn't, really? :D). Just `pacman -Sy clang` and then `export CC=clang;export CXX=clang++` before running `make`.
Thanks modprobe and xeroc. Compiling now with clang :)
-
Would you please help me to vote "usa" to be a delegate? +5% +5% +5% :) :) :)
https://bitsharestalk.org/index.php?topic=8148.0
-
Would you please help me to vote "usa" to be a delegate? +5% +5% +5% :) :) :)
https://bitsharestalk.org/index.php?topic=8148.0
Thanks. I will burn some of my income and donate to charity in m local church for pool kid in Africa
This comment is not directly aimed at you, but there are quite a few delegate claiming to give to charity. Some (xeroc) are more trustworthy than others, at some point donation plans will need to be more concrete/explicit. I think a delegates #1 job now is to fight through bugs and keep the infrastructure running and growing.
-
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.
Conclusions of testing:
Release works OK
Debug doesn't (like bytemaster said)
RelWithDebInfo (the default on my system, at least) does not work <-- that was my problem
If you explicitly do -DCMAKE_BUILD_TYPE=Release, it was fine
-
same problem here..
win 7 64Bit...
but 64 bit wallet do not work!!!
error msgbox on opening.
cryptillionaire,
What is exact error message you've got?
-
bitcube updated to 0.4.12.
Cheers!
-
I was testing a transaction after the successful update. I get this result:
cube (unlocked) >>> wallet_get_transaction c7126cfe
RECEIVED BLOCK FROM TO AMOUNT MEMO FEE ID
======================================================================================================================================================================
2014-09-06T00:57:25 PENDING bitcube bitcube 1.60000 BTSX 0.10000 BTSX c7126cfe
It is 'pending' and the balance not updated.
-
I downloaded the 64bit version from github and installed:
BitSharesX-0.4.12-x64.exe
After the database reindexed the wallet then tried to connect to the network. At that point I got an error:
"BitsharesX.exe has stopped working. A problem caused the program to stop working. Windows will close the program and notify you if a solution is available."
It was working under version 0.4.10
The PC is running Windows 8.1
64 bit OS, x64 based processor
Any thoughts?
-
I downloaded the 64bit version from github and installed:
BitSharesX-0.4.12-x64.exe
After the database reindexed the wallet then tried to connect to the network. At that point I got an error:
"BitsharesX.exe has stopped working. A problem caused the program to stop working. Windows will close the program and notify you if a solution is available."
It was working under version 0.4.10
The PC is running Windows 8.1
64 bit OS, x64 based processor
Any thoughts?
The Win 64bit is reported to have some problem. You may try the 32bit instead.
-
I downloaded the 64bit version from github and installed:
BitSharesX-0.4.12-x64.exe
After the database reindexed the wallet then tried to connect to the network. At that point I got an error:
"BitsharesX.exe has stopped working. A problem caused the program to stop working. Windows will close the program and notify you if a solution is available."
It was working under version 0.4.10
The PC is running Windows 8.1
64 bit OS, x64 based processor
Any thoughts?
The Win 64bit is reported to have some problem. You may try the 32bit instead.
Thanks, that worked.
-
network_add_node "188.226.195.137:60696" add
Running 0.4.12
-
Hey guys, i left dacsunlimited client untouched since 0.4.8 or 0.4.9 dont remember,
so my question is - is it safe to upgrade to 0.4.12 now, because im worried of possible bugs and is it safe to transfer funds from BTC 28.02 snapshot by this release?
-
Hey guys, i left dacsunlimited client untouched since 0.4.8 or 0.4.9 dont remember,
so my question is - is it safe to upgrade to 0.4.12 now, because im worried of possible bugs and is it safe to transfer funds from BTC 28.02 snapshot by this release?
from which wallet has you donated?
i would say in general yes. just export your wallet before you update and everything should be fine.
if you need to import from amory it is a pain in the ass.