BitShares 0.8.0 Feedback

[svk]

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.

I've fixed this this morning, was due to a change in the json response from the client.

[svk]

Short margin calls on expiry will buy up any asks up to 10% above feed.

Only due to a current bug, they should be at the feed price, at least that's what the people who know this better than me have told me (arhag, pc).

Margin called shorts however should execute at feed price +10%

[mdj]

Take a look at the bitUSD:BTS market right now. The market matching seem to not be fixed after all  :(  :'(



feed 222.3416 
Shorts at that price do not match with the buy bitUSD at 226 or 225;
Expired shorts do not match either.

Yea I've been watching this too for the last hour while working on the wallet, what makes everything even stranger is that there are trades happening but at ~246 BTS/bitUSD, more than 10% above the feed price at the time.

Here's a dedicated thread: https://bitsharestalk.org/index.php/topic,15668.msg201291.html#msg201291

Short margin calls on expiry will buy up any asks up to 10% above feed.

[svk]

Take a look at the bitUSD:BTS market right now. The market matching seem to not be fixed after all  :(  :'(



feed 222.3416 
Shorts at that price do not match with the buy bitUSD at 226 or 225;
Expired shorts do not match either.

Yea I've been watching this too for the last hour while working on the wallet, what makes everything even stranger is that there are trades happening but at ~246 BTS/bitUSD, more than 10% above the feed price at the time.

Here's a dedicated thread: https://bitsharestalk.org/index.php/topic,15668.msg201291.html#msg201291

[zerosum]

 Take a look at the bitUSD:BTS market right now. The market matching seem to not be fixed after all  :(  :'(



feed 222.3416 
Shorts at that price do not match with the buy bitUSD at 226 or 225;
Expired shorts do not match either.

[onceuponatime]

hmm, I did make an account on a mac computer a while ago and then made another with the same name on my PC...

I don't think your issue is 0.8.0 related.

Maybe you would be better off to start a new thread in the Technical Support area:
https://bitsharestalk.org/index.php/board,45.0.html 


Someone there will see your situation and help you out.

You should give as much information as possible, such as

- is the same account name registered in one wallet and not registered in the other?

- did you import your backup from the Mac to the PC?

- did you already collect some vested balances in the account on the MAC?

- anything else you can think of about your situation.

I'm sure that someone will have the solution for you.  Good luck  :)

[swedespade]

hmm, I did make an account on a mac computer a while ago and then made another with the same name on my PC...

[onceuponatime]

Do you have more than one account?

I have more than one account in my wallet, and I get that message on all but one account.

[swedespade]

Hi guys. I am trying to collect vested balanced, but the console is giving me this error...


>> wallet_collect_vested_balances swedishspade

20010 insufficient_funds: insufficient funds

    {"account_name":"swedishspade"}
    bitshares  wallet.cpp:2340 bts::wallet::wallet::collect_account_balances

    {"account_name":"swedishspade","sign":true}
    bitshares  wallet.cpp:2382 bts::wallet::wallet::collect_account_balances

    {}
    bitshares  common_api_client.cpp:6197 bts::rpc_stubs::common_api_client::wallet_collect_vested_balances

    {"command":"wallet_collect_vested_balances"}
    bitshares  cli.cpp:626 bts::cli::detail::cli_impl::execute_command

I also cant check my balance via the console

WINDOWS 8.1 | BITSHARES V 8.0 | REGISTERED USERNAME: swedishspade
last worked on Fab 20th 2015

Any ideas are much appreciated
Thanks!

[onceuponatime]

Is it just me, or is BTS:NOTE screen much much much slower than BTS:BitUSD?

They are both the same for me.

[bitmeat]

Is it just me, or is BTS:NOTE screen much much much slower than BTS:BitUSD?

[abit]

I recently hit some issues with 0.8.

I tried enabling RPC and this triggered a full blockchain re-download which took a few hours.
While this was happening, I set the logout automatically to a really big number like 40000000000 or something. This triggered a bug rendering the wallet completely unusable with the timing out screen rapidly appearing and disappearing. I couldn't fix this from removing the config etc and in the end had to restore from a backup wallet.

It could be a bug about bound overflow. I usually set the timeout to 99999999 with no problem (around 3 years).

The wallet parameter is stored in wallet database, not in config.json, so deleting the config file doesn't help.

Just a note, when the GUI getting unusable, you could try the command line if you're under linux/windows.

[mdj]

I recently hit some issues with 0.8.

I tried enabling RPC and this triggered a full blockchain re-download which took a few hours.
While this was happening, I set the logout automatically to a really big number like 40000000000 or something. This triggered a bug rendering the wallet completely unusable with the timing out screen rapidly appearing and disappearing. I couldn't fix this from removing the config etc and in the end had to restore from a backup wallet.

Since then I have been struggling to re-obtain my correct balances even after a full blockchain re-download and several rescans. I have used several of my backup files but the client seems to refuse to allow the balance to go above what it was at the time of backing up. Also, for some of my older backup files it just says "incorrect password" when I'm 100% I was entering it correctly. I am going to try and regenerate keys as a last resource as I have tried everything else from here: http://wiki.bitshares.org/index.php/Best_Practices/RecoverFunds

EDIT: I have successfully recovered all of my funds through re-generating keys :)

[xeroc]

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

Why there isn't a command to do that is beyond me. It's like a mandatory step for every upgrade.

Version 0.8.0 was the ONLY one that didn't do the reindexing after the update automatically ... and devs decided to have a reindex forced after all updates in future releases again ..

so sorry for the inconvenience .. won't happen again

[bitmeat]

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

Why there isn't a command to do that is beyond me. It's like a mandatory step for every upgrade.

[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  :D

[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 Expand

--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 Expand

--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 Expand


Bad Cast
Invalid cast from object_type to string
[email protected]:39:3875
○ [email protected]:44:23145
○ [email protected]:43:824
○ app.js:39:25606
○ [email protected]:7:45735
○ app.js:7:45907
○ [email protected]:7:82135
○ [email protected]:7:80649
○ [email protected]:7:82409
○ [email protected]:7:16490
○ [email protected]:7:25269
○ [email protected]: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 Expand

.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.

[gn1]

I'm on Mac OS X Yosemite, (16GB RAM) and updated to Bitshares 0.8.

Everything is working fine except the Exchange tab, where it becomes ridiculously slow. I can't trade because of the extreme lag. Any idea how to fix this problem?

[Chronos]

After bumping RAM up to 8gb, v0.8 is working well. Fully synced now. Good work!

However, if the client crashes, resuming the sync seems to hang sometimes.

[clayop]

0.8.1 for OSX is needed

[spartako]

Last night my delegate lost all connections and started to miss blocks. It is configured to not accept incoming connections.
It is the first time that happen to me with new versions (one time in August I had a similar problem)
Now it is synced again.

[pc]

I'm also getting "Network Problems" again (had it last night, but ws Ok this morning - but now back). Is there a way to check how many delegates are participating in my case and whether or not I am on a fork?

In the console, type get_info and look for these lines:

Code Select Expand


"blockchain_head_block_age": "8 seconds old",
"blockchain_average_delegate_participation": "82.11 %",


head_block_age should be less than a minute, and anything above 50% should mean you're on the good fork.

[liondani]

linux mint 17, 8 gb
very often when I make a transaction and I right click and click "reload" to see the right balance, the client will lost connection and the only way to fix it is to close and restart it....

[onceuponatime]

I'm also getting "Network Problems" again (had it last night, but ws Ok this morning - but now back). Is there a way to check how many delegates are participating in my case and whether or not I am on a fork?

[Akado]

Much more responsive than previous versions which would immediately freeze. It took some hours syncing but I can finally vote for delegates now! It feels good being able to vote after all this time! So happy to see the wallet working again, thanks for your hardwork!

At the moment, at the bottom, although it says blocks are synced it also says "Network Problems", dunno what it's about.

It took me a while to vote. You could simply have some kind of "checklist" on teh delegates list where you could choose the ones you wanted and at to a slate and then vote. Or go to the profile of a delegate and choose to vote for him or not next to the "make a payment" option. It would be easier that way. At the moment it feels you can't just do a quick search for the delegates you want and vote for them, that would be nice.

other than that it's way better than before, keep up the good work!

[svk]

I had a really hard time getting synced up on first launch, and during the night my delegate client lost all connections and started missing blocks. This only happened on my delegate server though, at the same time I updated the Bitsharesblocks api servers and they both synced up without issue.

[onceuponatime]

Wow. I run on Windows and  v0.8.0   downoaded very fast first try (after uninstalling 0.7.0) and has run perfectly for all day now.

I do have 16 gig on this machine,  and it is my experience on other machines that 4 gig always has issues.

[gnarl]

Win7x64 feedback

On my pc the install over 0.7.0 used 2.1gb of memory during the sync. It did not release the memory, and crashed when opening an exchange page.
Restarted.  Stuck on block 2115503. Total blocks are growing larger. Waited a while, then killed it. It wanted to rescan on startup...

On a different Win7 pc, first install, default location, it used 1.6gb of memory during the sync. It did not release the memory, and crashed when opening an exchange page.
Restarted. Yellow Network problems, but 20 connections. Stuck on block 2115555. Total blocks are growing larger.

The owner of the second system said "well I will not be risking any money on that ****** ****". and tried to uninstall it.

He closed it like a normal program with the X,  except bitshares doesn't close that way, it pops up a lame message and keeps running no matter what you click. Close does not kill it either....
He found the Uninstaller and ran it, but on the last page it said it did not remove everything. It did not uninstall. The Bitshares folder was still there, appdata\bitshares folder was still there, and the darn thing is still running in the task bar. The only thing it removed was the uninstaller, unins00.exe.
Unbelievable...

Is anyone even testing these builds on windows?

[ag]

I upgraded to 0.8.0 after the fork. the client got stuck on some block after the fork block. I restarted, still wouldn't sync. So now I'm rebuilding the block chain, and it will take a while, but I'm guessing it will be fine then.

[vikram]

Oh man this version is awesome, so so smooth! Nice work :)

OSX Yosemite with 8GB ram.

When was the involuntary 0.1BTS receive fee decided on? I think this should be re-thought because at the moment. there's nothing stopping a rich twisted person from setting their transaction fee to 0.1 and sending <0.1 payments to people thus reducing their balance overall.

It's not a receive fee, just a transaction fee. Right now you don't pay anything extra for including dust in a transfer.

[mdj]

Oh man this version is awesome, so so smooth! Nice work :)

OSX Yosemite with 8GB ram.

When was the involuntary 0.1BTS receive fee decided on? I think this should be re-thought because at the moment. there's nothing stopping a rich twisted person from setting their transaction fee to 0.1 and sending <0.1 payments to people thus reducing their balance overall.

[maqifrnswa]

had to delete my peers folder, but once done it connected fine

[bytemaster]

Hasn't connected to the network in over a day on my OS X.

Still getting a call price error, but I do not know if that is a result of the blocks not being synced.

I had to delete my chain folder and re download because I was stuck on a 0.6.0 fork that grew too large to undo. 

[gabes]

It seems Linux GUI version 0.8.1 works. It doesn't crashed yet. Need more testing time to confirm.

Linux GUI version 0.8 crashed. Previous version 0.7 works. (tested on Ubuntu 14.04)

Code Select Expand


Loading config from file: /home/gabo/.BitShares/config.json
QSslSocket: cannot resolve SSLv2_client_method
QSslSocket: cannot resolve SSLv2_server_method
/index.html
/css/app.css
/js/app.js
/locale-en.json
/img/xts-logo-xl-white-shadow.png
/img/logo-ico.svg
/img/xt-background.jpg
/webfonts/opensans-regular.woff
/webfonts/fontawesome-webfont.woff
/img/logo-ico.svg
QObject::startTimer: Timers can only be used with threads started with QThread
QPaintDevice: Cannot destroy paint device that is being painted
Segmentation fault


[joereform]

Hasn't connected to the network in over a day on my OS X.

Still getting a call price error, but I do not know if that is a result of the blocks not being synced.

[pgbit]

Win 8.1. Significantly snappier. Faster installation process with no reindexing / block syncing...

[fav]

got a little GUI issue since 0.7 - I run bitshares with  --lang=en_US in windows 7. the language is changing back to my native system language when I open the konsole.

[gabes]

Linux GUI version 0.8 crashed. Previous version 0.7 works. (tested on Ubuntu 14.04)

Code Select Expand


Loading config from file: /home/gabo/.BitShares/config.json
QSslSocket: cannot resolve SSLv2_client_method
QSslSocket: cannot resolve SSLv2_server_method
/index.html
/css/app.css
/js/app.js
/locale-en.json
/img/xts-logo-xl-white-shadow.png
/img/logo-ico.svg
/img/xt-background.jpg
/webfonts/opensans-regular.woff
/webfonts/fontawesome-webfont.woff
/img/logo-ico.svg
QObject::startTimer: Timers can only be used with threads started with QThread
QPaintDevice: Cannot destroy paint device that is being painted
Segmentation fault


[karnal]

So far, so good. Much faster than 0.6.0!

[pc]

One of the things I like about the latest upgrades, is there's no need to re-index the entire blockchain anymore. Is this a new feature?

A re-index is only necessary when there are changes in the internal database structures. 0.8.0 is only a bugfix release, so the database structure didn't change.

Future releases will most likely require re-indexing.

[Tuck Fheman]

       so much faster, so much stronger than poor old 0.7.0!

I walked out of the room, and v0.8.0 had poured me a drink (shaken, not shilled) and folded my fanboy suit!



so m00n!

[zerosum]

better than 0.7.0 for me personally (win7/i7/8gb). faster load. market swapping with everything loading up within 10 seconds at worst, 3-5 seconds on most tries.

i was never affected adversely by glitches in prior versions, so i can't comment on any of those fixes. it's just getting smoother with each new version for me!

So it is true!
     I thought it was a miracle.
            I upgraded to 0.8 from 0.7 and left my laptop unattended....
                          when I came back I saw it floating up in the air.... for good 3 sec.
I thought to myself "It cannot be true, you do not believe in miracles..."

     but it is true,
             it did indeed levitate

         due to the pure force that 0.8.0 put in it.

       so much faster, so much stronger than poor old 0.7.0!

[yellowecho]

Excellent experience so far!  Substantially faster and more stable

[kokojie]

One of the things I like about the latest upgrades, is there's no need to re-index the entire blockchain anymore. Is this a new feature?

[BunkerChainLabs-DataSecurityNode]

Upgraded.. works good..  +5%

[CryptoN8]

I upgraded to 0.8.0 from 0.7.0 on OSX. Says "Blocks are synced" and I moved some small amounts of BTS around between my test wallet. So far so good. I really need to learn more about the Exchange and get involved.

[Tuck Fheman]

better than 0.7.0 for me personally (win7/i7/8gb). faster load. market swapping with everything loading up within 10 seconds at worst, 3-5 seconds on most tries.

i was never affected adversely by glitches in prior versions, so i can't comment on any of those fixes. it's just getting smoother with each new version for me!

[Gentso1]

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

Was this released on the Devshare's chain for testing?

[vikram]

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