BitShares 0.7.0 Feedback

[gnarl]

Windows 7x64.  0.7.0
While loading the blockchain, the messages "Last Block was synced" and popup message "Catching up, processing # of #" is stuck and does not display progress. Leading you to think it has crashed.

It also appears to still have a memory leak, unless its supposed to use 1.666gb of memory while loading the blockchain.

When the log files stop getting bigger, I assume it has crashed and File\Quit and then eventually kill the process.

Second try at loading, it apparently downloaded 100days  of blockchain before running out of memory. After restarting it and letting it run for a couple hours, now used over 2gb of memory


default log had this error repeated a few times
7272015-03-24T01:14:45        th_a:?unnamed?          operator () ] Error during update checking: 11 eof_exception: End Of File
stringstream     {}     th_a  sstream.cpp:109 fc::stringstream::peek     {"str":""}     th_a  json.cpp:454 fc::json::from_string         MainWindow.cpp

p2p log was full of these while it was active
2015-03-24T01:55:21 p2p:message read_loop            read_loop ] disconnected 0 exception: unspecified   The file handle supplied is not valid
    {"message":"The file handle supplied is not valid"}     asio  asio.cpp:37 fc::asio::detail::read_write_handler_with_buffer::operator ()     {"len":16}
    p2p  stcp_socket.cpp:94 bts::net::stcp_socket::readsome         message_oriented_connection.cpp:182
2015-03-24T01:55:21 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"fc::asio::detail::read_write_handler_with_buffer::operator ()","hostname":"","thread_name":"asio","timestamp":"2015-03-24T01:55:21"},"format":"${message} ","data":{"message":"The file handle supplied is not valid"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":136,"method":"bts::net::stcp_socket::writesome","hostname":"","thread_name":"p2p","timestamp":"2015-03-24T01:55:21"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":245,"method":"bts::net::detail::message_oriented_connection_impl::send_message","hostname":"","thread_name":"p2p","timestamp":"2015-03-24T01:55:21"},"format":"unable to send message","data":{}}]}.  Closing connection.         peer_connection.cpp

The latest default.log file has grown to over 82mb, and the p2p log file is 98mb.  Is there no logfile size limit?

Deleted logs, config.json, node_config,json,  peers.leveldb files, and restarted. Same memory leak and stuck on block problem.

[karnal]

Thanks robrigo, I will wait for 0.8.0 which should be right around the corner and then give your suggestion a try

[robrigo]

Here's my experience with 0.7.0 so far:

- Download the linux version, realize it's just the cli, not the gui. Have to compile it.

- For some reason, BitShares 0.7.0 decides it's a good idea to resynchronize the whole blockchain. 5-6 hours go by.

- When I come back home and check on the progress, the wallet needs to be unlocked. No problem -- or so I thought;
   The unlock never really happened, the little dots were going for 7 minutes, at which point I closed the window.
   The process didn't die. A pkill BitS later and it's gone.

- Re-run BitShares, let it sync the remaining 14 days that were left. Realize ~90% of my funds are missing.


Guys, I'm sorry but this is easily the most buggy piece of software I've had the displeasure of interacting with over the last decade and a half. And I've used software. A lot.

The only two positive things:
  - The wallet appears to be very noticeably faster.
  - No segfault this time (previously [0.6.0] it segfaulted while syncing the blockchain)

FYI this is on Ubuntu 14.04 LTS.


Besides removing all files/dirs except wallet/, is there a way to convince the software to properly reflect my funds once again? I realize they are there, as long as I have the private keys (which I do, in backup plus the accounts do show up, it's the balance that's wrong)

Hey karnal. Here are some steps you can take to fix your balance:

http://wiki.bitshares.org/index.php/RecoveringFunds

In particular, try this for the effected accounts:

Code: [Select]

wallet_regenerate_keys ACCOUNT_NAME 12000


[karnal]

Here's my experience with 0.7.0 so far:

- Download the linux version, realize it's just the cli, not the gui. Have to compile it.

- For some reason, BitShares 0.7.0 decides it's a good idea to resynchronize the whole blockchain. 5-6 hours go by.

- When I come back home and check on the progress, the wallet needs to be unlocked. No problem -- or so I thought;
   The unlock never really happened, the little dots were going for 7 minutes, at which point I closed the window.
   The process didn't die. A pkill BitS later and it's gone.

- Re-run BitShares, let it sync the remaining 14 days that were left. Realize ~90% of my funds are missing.


Guys, I'm sorry but this is easily the most buggy piece of software I've had the displeasure of interacting with over the last decade and a half. And I've used software. A lot.

The only two positive things:
  - The wallet appears to be very noticeably faster.
  - No segfault this time (previously [0.6.0] it segfaulted while syncing the blockchain)

FYI this is on Ubuntu 14.04 LTS.


Besides removing all files/dirs except wallet/, is there a way to convince the software to properly reflect my funds once again? I realize they are there, as long as I have the private keys (which I do, in backup plus the accounts do show up, it's the balance that's wrong)

[Black Arrow]

After installing 0.7.0  on Windows I am getting the following message:

"An error occurred while trying to start. Please try restarting application."

Regardless of how many times I restart or try again after rebooting computer, I continue to get this same message.

I have also tried renaming config.json. When I restart it creates a new config.json file but I continue to get the same error message.

Any suggestions on what to try next?

[milkmeat]

the client seems lost connection very easily.
Mac version 0.7a
On bottom right corner it becomes "not connected" every few minutes, I have to restart the client to reconnect.

[Reiner]

I dont find nowhere how to upgrade.
Have i deinstall first the old version?
Or can i just click the new *.exe
Have i to load the blockchain again? My internetconnection is very slow.
Edit later ...
So i just install without deinstalling.
Installation works fine. First version that work for me on my old xp laptop
But what is that a new version 7-a?
ok ...

[CryptoN8]

Any hints on getting it to sync? It appears to be stuck, and I have tried a rescan from the Console.


I'm running version: (with the -a patch notification after upgrade install from 0.6.2)

Code: [Select]

{
  "blockchain_name": "BitShares",
  "blockchain_description": "Decentralized Exchange",
  "client_version": "0.7.0",
  "bitshares_revision": "480b4ec1df374b4b81b814ac8ba3eab013ff93dc",
  "bitshares_revision_age": "4 days ago",
  "fc_revision": "374f141f0a31fb362a2eb3fc982acf57107cc5bc",
  "fc_revision_age": "26 days ago",
  "compile_date": "compiled on Mar 17 2015 at 17:07:43",
  "boost_version": "1.57",
  "openssl_version": "OpenSSL 1.0.2 22 Jan 2015",
  "build": "osx 64-bit"
}
UPDATE / FIXED:
https://bitsharestalk.org/index.php?topic=15114.msg195525#msg195525

[abit]

I do notice however though during startup that the disk access for whatever reason is extremely high. Why so much disk access? Is there some kind of complete reindexing taking place at startup?

The client loads the full chain database's data and indexes from disk into memory or into some kind of cache at startup.

[sudo]

https://github.com/BitShares/web_wallet/issues/660

can't display the help file on market page

[sudo]

please  provide a way to  update path  manually

0.7.0-a patch  can‘t check update  on my network
so i find some good guy to transfer  to me
two files
web.json &web.dat

the json cotains

Code: [Select]

{
  "majorVersion": 0,
  "forkVersion": 7,
  "minorVersion": 0,
  "patchVersion": 97,
  "signatures": [
    "2071d654dfc5b180debd3ed8e9825c45df16435a5064d886d2d413a37291bb9a65351170e85eb65d78d5a65b6c0bfd4a544ddaa1c48c364957032152fa625c9911",
    "1f2b77f98303cefb0524575bcd0cadc3a2508964f3093b45bc101e4eb8d7355ab137d5dd9086c9af1851befefa64e69317a5d57ac6d700baffc7a28028b347ff05"
  ],
  "releaseNotes": "Fixes transfers to subaccounts and several small display issues\n",
  "updatePackageUrl": "https://bitshares.org/0.7.0-a.pak",
  "timestamp": "2015-03-18T18:57:45"
}


[pc]

That seems to be the case. And I see no rationale for this rule in any shape or form.

It's not a rule in itself. It is an unfortunate side effect of the market rules concerning shorts, namely that shorts with a high APR are preferred over those with low APR.

The market engine is being worked on. In the new version, shorts at the price feed will be ordered by APR and shorts with a limit below the feed will be ordered by their limit. See https://github.com/BitShares/bitshares/issues/1443 .

[ag]

1.

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

Interest of those shorts are too low. Need to be higher than other shorts.

Ohh...Marvelous! Outstanding! You guys  are on a hot streak  in the last 5-6 mo...streak of novel ideas how to kill the market, that is.

So, one guy put a 50% interest short order on bitBTC with price limit at 60000 BTS/BitBTC. I happen to have to grandfather my short. Are you telling me I can't grandfather my short unless I put more than 50% interest rate ? Come on... this has to change NOW. It's an emergency.

By the way, the 60000 BTS/BitBTC 50% interest order is for 0.002 BTC. Does it really block ALL creation of new bitBTC unless interest is higher than 50% ? If so, this is just plainly unforgivable. I'm gonna spoil all the other markets also.

That seems to be the case. And I see no rationale for this rule in any shape or form.

[inarizushi]

1.

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

Interest of those shorts are too low. Need to be higher than other shorts.

Ohh...Marvelous! Outstanding! You guys  are on a hot streak  in the last 5-6 mo...streak of novel ideas how to kill the market, that is.

So, one guy put a 50% interest short order on bitBTC with price limit at 60000 BTS/BitBTC. I happen to have to grandfather my short. Are you telling me I can't grandfather my short unless I put more than 50% interest rate ? Come on... this has to change NOW. It's an emergency.

By the way, the 60000 BTS/BitBTC 50% interest order is for 0.002 BTC. Does it really block ALL creation of new bitBTC unless interest is higher than 50% ? If so, this is just plainly unforgivable. I'm gonna spoil all the other markets also.

[BunkerChainLabs-DataSecurityNode]

I do notice however though during startup that the disk access for whatever reason is extremely high. Why so much disk access? Is there some kind of complete reindexing taking place at startup?

Also re the memory usage.. @tonyk2.. the more markets you open the more data you are loading the more gets put into memory. I think this might have been done for the sake of real time data updates going faster rather than attempting to write updates to your hard disk. Updates come in.. more data gets feed into memory depending on what screen you left it on I suppose. In my test I only went to the one market I normally go to.. BTS/BitUSD.

With that in mind.. I am not a programmer.. but I cannot think of an elegant solution from an infrastructure perspective in a p2p network where you don't have that situation in an end client. The only alternative is to centralize that.. which as you know would not be acceptable to a decentralized network... unless...

The other alternative to this that would certainly speed it all up and reduce client resources is going to a web solution.. which we have seen.. it's lighter and puts all the data crunching at the server level instead of the client. That might be what you want to focus on if you do not have system resources available. Running 32bit can't be helping you much either.

I don't know how technically feasible it is to move a client wallet to a web wallet.. far as I know currently it's not possible.. but once it is then it's going to be awesome.

[zerosum]

1.

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

Interest of those shorts are too low. Need to be higher than other shorts.

Ohh...Marvelous! Outstanding! You guys  are on a hot streak  in the last 5-6 mo...streak of novel ideas how to kill the market, that is.




2. Unfortunately I cannot confirm the good reports of improved performance like the guys up the thread.
win7/32 the memory usage starts at ~750MB for me and climbs to ~1500MB in 10-15 min or so, of the client running and opening several markets...Interestingly enough, on the 3rd restart the RAM growth is much slower now....it might take more than an hour to double this time... only 988MB after 45 min.

[abit]

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

Interest of those shorts are too low. Need to be higher than other shorts.

[lovejoy]

0.7.0 is smooth like butter!  Faster than ever before, like some ninja was in there assassinating memory leaks or something!

Anyways.. going to take the bitUSD I just bought and go to www.cryptofresh.com and get me a t-shirt now.

   -- early indications are that as the client improves, so do sales!     Thanks DSN!

[ag]

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

[Brekyrself]

Has anything changed when claiming vested balances?

No I've collected them today using 0.7.0.
Are you using wallet_collect_vested_balances userName ?

Simply restarted the client and it worked, odd.

[yellowecho]

Has anything changed when claiming vested balances?

No I've collected them today using 0.7.0.
Are you using wallet_collect_vested_balances userName ?

[Brekyrself]

*restarted the client and working again*

Has anything changed when claiming vested balances?  I tried it today with no luck and also did a rescan with no vesting balances being unlocked.  The last time I claimed was ~9 days ago on the previous client.

Doing a get_info looks like I am not on a fork:

{
  "blockchain_head_block_num": 2071710,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2015-03-19T20:09:40",
  "blockchain_head_block_id": "4bd660567ed6f9e9f1b2e515355898d870e54388",
  "blockchain_average_delegate_participation": "95.28 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": "2,504,344,286.23687 BTS",
  "blockchain_blocks_left_in_round": 2,
  "blockchain_next_round_time": "at least 15 seconds in the future",
  "blockchain_next_round_timestamp": "2015-03-19T20:10:00",
  "blockchain_random_seed": "3cf904698c9b168440137100371684c9d9791baf",
  "client_data_dir": "C:/Users/Brekyrself/AppData/Roaming/BitShares",
  "client_version": "0.7.0",
  "network_num_connections": 3,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-03-19T20:09:45",
  "ntp_time_error": -70.801544000000007,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-03-31T09:57:11",
  "wallet_last_scanned_block_timestamp": "2015-03-19T20:09:40",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

[yellowecho]

After a reboot I'm get getting connected.  Can someone provide me with a command and some nodes?

[Troglodactyl]

Any idea what the patch to 0.7.0-a does?

I guess it's an updated version to also include the changes made to the web_wallet .. they missed those for 0.7.0 AFAIK

edit: can't find that patch .. where is it?

I believe he's referring to the auto-downloading GUI update: https://github.com/BitShares/web_wallet/releases/tag/0.7.0-a

It added the "Make a payment" button and improved the transfer page, apparently.

[monsterer]

Any idea what the patch to 0.7.0-a does?

I guess it's an updated version to also include the changes made to the web_wallet .. they missed those for 0.7.0 AFAIK

edit: can't find that patch .. where is it?

After you download the win32 0.7.0 and install, it asks if you want to upgrade to the 0.7.0-a patch

[xeroc]

Any idea what the patch to 0.7.0-a does?

I guess it's an updated version to also include the changes made to the web_wallet .. they missed those for 0.7.0 AFAIK

edit: can't find that patch .. where is it?

[monsterer]

Any idea what the patch to 0.7.0-a does?

[pc]

Bought some bitUSD at the same ASK for the lowest price.. order processed right away to withdraw my BTS.. but my buy order just sat there.

That may have been due to price rounding. I. e. the internal price of the offer you tried to match was slightly higher than what was displayed and/or what you put in your order.

[Tuck Fheman]

win7/8gb, running much faster. charts loading very fast now. switching between tabs is very smooth. very impressed.

the only issue i see is in the console :

Code: [Select]

>> get_rich_quick tuckfheman-com

{
  "unlocked": false
}


[BunkerChainLabs-DataSecurityNode]

Another thing to note.. my memory usage floats around 671 to 675MB.

CPU around 2-4% utilization on standby.. about double that of Google Chrome running in the background.

I don't know if these are targets you were trying to achieve or not.

Also I notice when I click around the Exchange area quickly the client no longer crashes. In 0.6.2 if I didn't wait to allow all the data to load before clicking on another section it would often crash. Now the client seems to handle that condition better.

Was happy I didn't have to redownload/reindex the whole db again on upgrade. Those are brutal.

Will post anything else I notice.  though!

[jamesc]

Installed over top of the existing client just fine. The wallet is more responsive to scrolling around. Exchange is also faster. I liked to robots better than what we have now.

Seems like you guys improved the speed quite a bit. Good job!

Not robots... They are Snowflakes.

[yellowecho]

OSX here with 16GB RAM.  Downloaded and installed quick and easy.  Everything loads quickly and haven't experienced any bugs yet.

[BunkerChainLabs-DataSecurityNode]

Installed no problem on Windows 8.1 system with 6GB RAM and SSD drive over 0.6.2.

Loaded up.. logged in no problem.

Went to bitassets, loaded up a little snapper.. thats nice.

Bought some bitUSD at the same ASK for the lowest price.. order processed right away to withdraw my BTS.. but my buy order just sat there.

It took a full 8 minutes until the BitUSD arrive to my wallet.

Normally they was done instantaneously.. but I was doing the opposite normally and buying BTS.

Anyways.. going to take the bitUSD I just bought and go to www.cryptofresh.com and get me a t-shirt now.

[MisO69]

Installed over top of the existing client just fine. The wallet is more responsive to scrolling around. Exchange is also faster. I liked to robots better than what we have now.

Seems like you guys improved the speed quite a bit. Good job!

[vikram]

So if I understand correctly this only includes the essential bug fixes, and the rest of what was DVS/0.7.0 became DVS/0.8.0?

Will 0.8.0 be released for DVS first?

Yes on both.

[emski]

0.7.0 looks stable.

[fav]

I'd like to see an additional torrent with a snapshot of the current chain. many people have issues syncing from 0.

[svk]

So if I understand correctly this only includes the essential bug fixes, and the rest of what was DVS/0.7.0 became DVS/0.8.0?

Will 0.8.0 be released for DVS first?

[JA]

Took it's time to load like the previous versions.
Everything loads fast except some market pages but still under 10 seconds.
And now i can scroll on the market pages without lagging.

Quitting the client still causes it to freeze (windows) and i have to close it via task manager

[vikram]

https://github.com/BitShares/bitshares/releases/tag/bts%2F0.7.0

Previous feedback thread: https://bitsharestalk.org/index.php?topic=14545.msg189123#msg189123

Version number was bumped to 0.7 due to hardfork.