BitShares 0.8.0 Feedback

[xeroc]

How exactly should I perform these actions in a OSX environment???
thanks

In the folder "Library/Application Support/BitShares" there is a subfolder called "chains" ... remove just that one!!

[Bitty]

Blockchain stuck at block 2074788.
Mac client.
Upgraded to 0.8.

What can I do?

backup wallet
remove chain folder


restart client and let resync

works for us

thanks
how does one back up the client without making mistakes?

How exactly should I perform these actions in a OSX environment???
thanks

[yellowecho]

For some reason 0.8.0 is running extremely slow for me now especially the NOTE and other UIA markets.  It's not crashing but seems very unstable. 

I'm running 16GB RAM so its not a memory issue but acts similar.  Any ideas?

Which UI version are you on?  I suggest removing UI updates from the file menu.  You can get them back just as easily, so it's worth a try.

I'm on 0.8.1, but it seemed like the 0.8.1-a update had a few some issues.

Awesome- removing the updates fixed it!  Thanks!  It did take NOTE:BTS away from the featured markets page and the NOTE depth chart isn't zoomed but at least it's functional again 

[abit]

My win 0.8.0-a (and 0.8.0 builds) are stuck on the wrong fork, is there anything I can do without having to delete and regrab the entire chain?

restart with

Code: [Select]

--rebuild-index
may only work with the bitshares_client.exe (nonGUI)

I think it wont work if he is more than 360 blocks after the hard fork block.
Upgrade to 0.8.1 and resync should work.

//Edit:
Reindex would work, but only after upgraded to 0.8.1 or updated checkpoints.json like this post https://bitsharestalk.org/index.php?topic=15218.msg196858#msg196858 .
With 0.8.0 and old checkpoints.json, the client will still think the wrong fork is valid, and will stuck again.

[xeroc]

My win 0.8.0-a (and 0.8.0 builds) are stuck on the wrong fork, is there anything I can do without having to delete and regrab the entire chain?

restart with

Code: [Select]

--rebuild-index
may only work with the bitshares_client.exe (nonGUI)

[monsterer]

My win 0.8.0-a (and 0.8.0 builds) are stuck on the wrong fork, is there anything I can do without having to delete and regrab the entire chain?

[abit]

Blockchain stuck at block 2074788.
Mac client.
Upgraded to 0.8.

What can I do?

Users who're using 0.8.0 may run into the wrong fork, then have to delete the chain folder and re-sync from scratch (and may run into the wrong fork again). So it's recommended to release a 0.8.1 binary for MacOS.
It's also recommended that all users upgrade to version 0.8.1
@vikram

[Troglodactyl]

For some reason 0.8.0 is running extremely slow for me now especially the NOTE and other UIA markets.  It's not crashing but seems very unstable. 

I'm running 16GB RAM so its not a memory issue but acts similar.  Any ideas?

Which UI version are you on?  I suggest removing UI updates from the file menu.  You can get them back just as easily, so it's worth a try.

I'm on 0.8.1, but it seemed like the 0.8.1-a update had a few some issues.

[yellowecho]

For some reason 0.8.0 is running extremely slow for me now especially the NOTE and other UIA markets.  It's not crashing but seems very unstable. 

I'm running 16GB RAM so its not a memory issue but acts similar.  Any ideas?

[Bitty]

Blockchain stuck at block 2074788.
Mac client.
Upgraded to 0.8.

What can I do?

backup wallet
remove chain folder


restart client and let resync

works for us

thanks
how does one back up the client without making mistakes?

[Tuck Fheman]

Blockchain stuck at block 2074788.
Mac client.
Upgraded to 0.8.

What can I do?

backup wallet
remove chain folder
restart client and let resync

works for us

[Tuck Fheman]

When using "burn records" on someone's wall, why is it changing to "against" every time no matter what is selected (for/against)?

Which color indicates your selection (green/white)? No matter which we try it ends up as same result, against.

[Bitty]

Blockchain stuck at block 2074788.
Mac client.
Upgraded to 0.8.

What can I do?

[Tuck Fheman]

Getting this (7 times I believe since updating to 0.8.0/0.8.1) ...

Code: [Select]

Bad Cast
Invalid cast from object_type to string
getStackTrace@app.js:39:3875
 ○ request@app.js:44:23145
 ○ get_block_transactions@app.js:43:824
 ○ app.js:39:25606
 ○ i@app.js:7:45735
 ○ app.js:7:45907
 ○ $eval@app.js:7:82135
 ○ $digest@app.js:7:80649
 ○ $apply@app.js:7:82409
 ○ f@app.js:7:16490
 ○ r@app.js:7:25269
 ○ onload@app.js:7:25809
7 bad_cast_exception: Bad Cast
Invalid cast from object_type to string
    {"type":"object_type"}
    bitshares  variant.cpp:471 fc::variant::as_string
I'm going to guess it has something to do with (how we're) using the memo field? (because we've been using it lately and never have before)

[ag]

My log file grew to 10+ gb in less than 48 hours. It took up all my disk space. then my progam didn't exit cleanly. I had to resync the whole chain  . My new log file is growing again almost at 1gb in a few hours.

Code: [Select]

.bitshares/logs# du -h -d1
4.0K    ./blockchain
4.0K    ./rpc
243M    ./default
620M    ./p2p
863M    .

 the exceptions dir also gets large. it's already at 200mb. Never had this issue before.