BitShares Forum

Main => General Discussion => Topic started by: vikram on February 26, 2015, 03:53:44 am

Title: BitShares 0.6.2 Feedback
Post by: vikram on February 26, 2015, 03:53:44 am
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.6.2

Please only use this thread to post constructive feedback that may be useful to the development team.
Title: Re: BitShares 0.6.2 Feedback
Post by: xeroc on February 26, 2015, 08:17:22 am
Whats the name of the tag in the public.data field to switch titan/non-titan?
Title: Re: BitShares 0.6.2 Feedback
Post by: JA on February 26, 2015, 10:14:39 am
Quote
Robohashes have been replaced with more reliable Identicons
i prefer that  +5% looks nice

Quote
Blockchain history will be replayed on upgrade
Took my windows 64 bit 8gb an hour

The rest runs blazing fast and loads instantly

The transaction history doesn't show the identicons, don't know if that is intended
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on February 26, 2015, 03:05:59 pm
 +5%  I love the new icons. 

 +5% Everything loads much, much faster.  Great improvements. 

Still no Recent Transactions.  reload doesn't help.

oop  spoke too soon regarding the speed. 
upon first entering the exchange, everything loads very quickly.
If I enter a market and then hit back, or click exchange again,  it loads very slow,  >10secs
edit: coming from the Delegate page or the Transfer page, the Exchange page loads quickly.  coming from the Dashboard or from a market page, it loads very slowly.

If you click on a preferred market above the graph portion of the button, It takes you to the correct market.  However if you click on the graph portion of the button it takes you to bitSiliver market, regardless of which preferred market you clicked on.
Title: Re: BitShares 0.6.2 Feedback
Post by: cn-members on February 26, 2015, 04:44:10 pm
One suggestion from the chinese community: the content of app.js.map is in plain text,  it can be compressed and cached locally to save the bandwidth. 

On the other hand,  I also think the identicon is great,  and I wonder whether the identicon can be used in reverse: input the identicon figure and it can be reversed into an account name? I found some discussion elsewhere (http://crypto.stackexchange.com/questions/15932/reverse-an-identicon-to-its-source-string) and guess it is possible right? I think it could be great if we can use mobile wallet to scan identicon and complete transaction.
Title: Re: BitShares 0.6.2 Feedback
Post by: yellowecho on February 26, 2015, 05:48:31 pm
Much faster speed-  I was able to replay and download the entire chain in about an hour.  And the new identicons are awesome!  +5% If they could be reversed and scanned like QR codes it'd be really cool  8) 
Title: Re: BitShares 0.6.2 Feedback
Post by: vikram on February 26, 2015, 06:01:25 pm
Whats the name of the tag in the public.data field to switch titan/non-titan?

It's a separate field called meta_data in the account_record. Actually, I am not sure if we provide a way to update it.. if you can't find a way you can make an issue for it.
Title: Re: BitShares 0.6.2 Feedback
Post by: Pheonike on February 26, 2015, 06:41:39 pm

Not a critic, but feature add,

Can we add send Max amount or send All option  for a transfer.
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on February 26, 2015, 07:52:18 pm
win7x64
can't change accounts in top right from any of the tabs.

Only place it works is inside a market trading page.
Title: Re: BitShares 0.6.2 Feedback
Post by: vlight on February 26, 2015, 08:04:14 pm
Can't find how to view public key of account in the address book.
Title: Re: BitShares 0.6.2 Feedback
Post by: fluxer555 on February 26, 2015, 08:04:49 pm
One suggestion from the chinese community: the content of app.js.map is in plain text,  it can be compressed and cached locally to save the bandwidth. 

On the other hand,  I also think the identicon is great,  and I wonder whether the identicon can be used in reverse: input the identicon figure and it can be reversed into an account name? I found some discussion elsewhere (http://crypto.stackexchange.com/questions/15932/reverse-an-identicon-to-its-source-string) and guess it is possible right? I think it could be great if we can use mobile wallet to scan identicon and complete transaction.

Identicons were not built with internal verification systems, so obtaining the wrong data from an imperfect picture is very possible, even likely. In other words, this is a bad idea. If we want this functionality, QR codes already accomplish this and have all the verification safegaurds in place.
Title: Re: BitShares 0.6.2 Feedback
Post by: ubits on February 26, 2015, 08:25:22 pm
I have used almost every version of the wallet form the beginning with few issues. Starting with 0.61  lost account names, balances and transactions

0.62 blockchain synced quickly, under an hour, and  account names show, but no balances or transactions

Mavericks, fully synced 0.62
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on February 26, 2015, 08:50:16 pm
win7x64
can't change accounts in top right from any of the tabs.

Only place it works is inside a market trading page.
I've created issue for this bug https://github.com/BitShares/web_wallet/issues/635
This will be fixed in the next release.
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on February 26, 2015, 08:51:52 pm
I have used almost every version of the wallet form the beginning with few issues. Starting with 0.61  lost account names, balances and transactions

0.62 blockchain synced quickly, under an hour, and  account names show, but no balances or transactions

Mavericks, fully synced 0.62
Do balances and transactions return when you right click and select reload?
Title: Re: BitShares 0.6.2 Feedback
Post by: yellowecho on February 26, 2015, 09:57:53 pm
I have used almost every version of the wallet form the beginning with few issues. Starting with 0.61  lost account names, balances and transactions

0.62 blockchain synced quickly, under an hour, and  account names show, but no balances or transactions

Mavericks, fully synced 0.62
Do balances and transactions return when you right click and select reload?

This.  I had to refresh after syncing everything.
Title: Re: BitShares 0.6.2 Feedback
Post by: liondani on February 26, 2015, 10:41:18 pm
I loved the robohashes but the indeticons are awesome too and much more professional !   +5%
Title: Re: BitShares 0.6.2 Feedback
Post by: vlight on February 27, 2015, 09:56:13 am
The blockchain was synced faster, however transaction scanning seems to be slower.  ???
Title: Re: BitShares 0.6.2 Feedback
Post by: ubits on February 27, 2015, 12:52:13 pm
I have used almost every version of the wallet form the beginning with few issues. Starting with 0.61  lost account names, balances and transactions

0.62 blockchain synced quickly, under an hour, and  account names show, but no balances or transactions

Mavericks, fully synced 0.62
Do balances and transactions return when you right click and select reload?
When I right click, a box displays briefly to Go Back or Reload, but it disapears before I can click.  Is there a command in console to do the same?

PS managed to click the Reload and everything restored instantly :-)
Title: Re: BitShares 0.6.2 Feedback
Post by: oco101 on February 27, 2015, 11:28:58 pm
I manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what  I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. Thanks
Title: Re: BitShares 0.6.2 Feedback
Post by: hpenvy2 on February 28, 2015, 12:35:48 am
https://bitsharestalk.org/index.php?topic=14536.msg189031#msg189031

Remove any wallet reference and call it exchange.
Title: Re: BitShares 0.6.2 Feedback
Post by: joele on February 28, 2015, 03:03:11 am
1. In the Exchange, when I first click the bitUSD:BTS chart it open the bitSILVER:BTS trading, then it hang and crash afterwards.

2. I sold all the amount of coins and it keep some dust
0.000001 CFSGOLD
0.000001 GOLD
0.0001 SILVER
Title: Re: BitShares 0.6.2 Feedback
Post by: yellowecho on February 28, 2015, 07:18:51 am
1. In the Exchange, when I first click the bitUSD:BTS chart it open the bitSILVER:BTS trading, then it hang and crash afterwards.

2. I sold all the amount of coins and it keep some dust
0.000001 CFSGOLD
0.000001 GOLD
0.0001 SILVER

I've experienced these as well
Title: Re: BitShares 0.6.2 Feedback
Post by: mdj on February 28, 2015, 12:26:16 pm
Great improvements, generally feels a lot smoother/user friendly!

One critic was when it was reloading the blockchain, the update patch (0.6.2a) notification caused the client to freeze so I did have to force restart and then it worked fine.

Good job :)
Title: Re: BitShares 0.6.2 Feedback
Post by: onceuponatime on March 01, 2015, 11:03:11 pm
I manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what  I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. Thanks

I am having the same problem. Can't log in.
Title: Re: BitShares 0.6.2 Feedback
Post by: bitAndy on March 02, 2015, 04:17:15 am
I've just downloaded 0.6.2, and then downloaded a patch update to 0.6.2-b. Now 'unlock.desc_title' sits above the passphrase box, where bitshares decentralized exchange should be.
Title: Re: BitShares 0.6.2 Feedback
Post by: oco101 on March 02, 2015, 04:21:30 am
I manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what  I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. Thanks

I am having the same problem. Can't log in.
Let me know if  you find a fix. I'm thinking to go back to the wallet backup and reinstall everything .....again
Title: Re: BitShares 0.6.2 Feedback
Post by: onceuponatime on March 02, 2015, 05:08:17 am
I manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what  I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. Thanks

I am having the same problem. Can't log in.
Let me know if  you find a fix. I'm thinking to go back to the wallet backup and reinstall everything .....again

I just deleted everything but the wallet folder and reinstalled. Same problem.
Title: Re: BitShares 0.6.2 Feedback
Post by: oco101 on March 02, 2015, 05:10:26 am
I manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what  I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. Thanks

I am having the same problem. Can't log in.
Let me know if  you find a fix. I'm thinking to go back to the wallet backup and reinstall everything .....again

I just deleted everything but the wallet folder and reinstalled. Same problem.
I did the same thing. And same problem can't log on !!
Title: Re: BitShares 0.6.2 Feedback
Post by: Gentso1 on March 03, 2015, 01:59:15 am
love the new icons
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 03, 2015, 03:46:50 pm
Account history inaccessible.   No account transaction history is viewable in any account from the GUI pages.  Reload does nothing.

Only some of my accounts history is accessible from Console ....   for example entering "history xeldal2"  produces nothing.  It just sits there.
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on March 03, 2015, 04:09:16 pm
Account history inaccessible.   No account transaction history is viewable in any account from the GUI pages.  Reload does nothing.

Only some of my accounts history is accessible from Console ....   for example entering "history xeldal2"  produces nothing.  It just sits there.

Is it fully synchronized? What is your OS and wallet version?
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 03, 2015, 04:12:11 pm
Account history inaccessible.   No account transaction history is viewable in any account from the GUI pages.  Reload does nothing.

Only some of my accounts history is accessible from Console ....   for example entering "history xeldal2"  produces nothing.  It just sits there.

Is it fully synchronized? What is your OS and wallet version?

Yes fully synced.. version 0.6.2  Win7x64
It works for other accounts in the same client... just not that one.

125 JSON March 3, 2015 at 11:13:25 AM EST
Parse error: Unterminated string
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on March 03, 2015, 08:17:45 pm

Yes fully synced.. version 0.6.2  Win7x64
It works for other accounts in the same client... just not that one.

125 JSON March 3, 2015 at 11:13:25 AM EST
Parse error: Unterminated string

I guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 03, 2015, 08:28:31 pm

Yes fully synced.. version 0.6.2  Win7x64
It works for other accounts in the same client... just not that one.

125 JSON March 3, 2015 at 11:13:25 AM EST
Parse error: Unterminated string

I guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
How is this done?  Clicking on "show details" doesn't seem to do anything .
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on March 03, 2015, 10:27:49 pm
I guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
How is this done?  Clicking on "show details" doesn't seem to do anything .

Probably this error doesn't have any details.
Do you have access to the log files? If you do, could look if default.log references this error?
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 04, 2015, 12:29:41 am
I guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
How is this done?  Clicking on "show details" doesn't seem to do anything .

Probably this error doesn't have any details.
Do you have access to the log files? If you do, could look if default.log references this error?

This is from the default.log file after I try and initiate "history xeldal2" from the console.
Code: [Select]
2015-03-04T00:26:12        th_a:?unnamed?          log_message ] Message from GUI: js error: JSON Parse error: Unterminated string
parse@[native code]
 ○ S@http://127.0.0.1:59187/js/app.js:5:1792
 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948
 ○ http://127.0.0.1:59187/js/app.js:6:4375
 ○ f@http://127.0.0.1:59187/js/app.js:4:59169
 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357
 ○ e@http://127.0.0.1:59187/js/app.js:6:9402
 ○ i@http://127.0.0.1:59187/js/app.js:6:45333
 ○ http://127.0.0.1:59187/js/app.js:6:45505
 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532
 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046
 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806
 ○ f@http://127.0.0.1:59187/js/app.js:6:15887
 ○ r@http://127.0.0.1:59187/js/app.js:6:24666
 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:35
2015-03-04T00:26:12        th_a:?unnamed?          log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined)
Utilities.cpp:35
2015-03-04T00:26:14 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:732
2015-03-04T00:26:27 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:732
2015-03-04T00:26:30        th_a:?unnamed?          log_message ] Message from GUI: js error: JSON Parse error: Unterminated string
parse@[native code]
 ○ S@http://127.0.0.1:59187/js/app.js:5:1792
 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948
 ○ http://127.0.0.1:59187/js/app.js:6:4375
 ○ f@http://127.0.0.1:59187/js/app.js:4:59169
 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357
 ○ e@http://127.0.0.1:59187/js/app.js:6:9402
 ○ i@http://127.0.0.1:59187/js/app.js:6:45333
 ○ http://127.0.0.1:59187/js/app.js:6:45505
 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532
 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046
 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806
 ○ f@http://127.0.0.1:59187/js/app.js:6:15887
 ○ r@http://127.0.0.1:59187/js/app.js:6:24666
 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:35
2015-03-04T00:26:30        th_a:?unnamed?          log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined)
Utilities.cpp:35
2015-03-04T00:26:34 ntp:request_time_task          request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:77
2015-03-04T00:26:34 ntp:request_time_task          request_now ] sending request to 66.175.209.17:123 ntp.cpp:81
2015-03-04T00:26:34     ntp:ntp_read_loop            read_loop ] received ntp reply from 66.175.209.17:123 ntp.cpp:147
2015-03-04T00:26:34     ntp:ntp_read_loop            read_loop ] ntp offset: -3039805, round_trip_delay 137967 ntp.cpp:161
2015-03-04T00:26:34     ntp:ntp_read_loop            read_loop ] ntp_delta_time updated to -3039805 ntp.cpp:177
Title: Re: BitShares 0.6.2 Feedback
Post by: milkmeat on March 04, 2015, 03:23:09 pm
an UI issue

When I click a "bts:account/transfer/..." link from browser to jump into the client's transfer page. The account logo is not displayed.
It only shows when you key in the account name from the first letter.
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on March 04, 2015, 04:28:15 pm
I guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
How is this done?  Clicking on "show details" doesn't seem to do anything .

Probably this error doesn't have any details.
Do you have access to the log files? If you do, could look if default.log references this error?

This is from the default.log file after I try and initiate "history xeldal2" from the console.
Code: [Select]
2015-03-04T00:26:12        th_a:?unnamed?          log_message ] Message from GUI: js error: JSON Parse error: Unterminated string
parse@[native code]
 ○ S@http://127.0.0.1:59187/js/app.js:5:1792
 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948
 ○ http://127.0.0.1:59187/js/app.js:6:4375
 ○ f@http://127.0.0.1:59187/js/app.js:4:59169
 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357
 ○ e@http://127.0.0.1:59187/js/app.js:6:9402
 ○ i@http://127.0.0.1:59187/js/app.js:6:45333
 ○ http://127.0.0.1:59187/js/app.js:6:45505
 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532
 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046
 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806
 ○ f@http://127.0.0.1:59187/js/app.js:6:15887
 ○ r@http://127.0.0.1:59187/js/app.js:6:24666
 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:35
2015-03-04T00:26:12        th_a:?unnamed?          log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined)
Utilities.cpp:35
2015-03-04T00:26:14 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:732
2015-03-04T00:26:27 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:732
2015-03-04T00:26:30        th_a:?unnamed?          log_message ] Message from GUI: js error: JSON Parse error: Unterminated string
parse@[native code]
 ○ S@http://127.0.0.1:59187/js/app.js:5:1792
 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948
 ○ http://127.0.0.1:59187/js/app.js:6:4375
 ○ f@http://127.0.0.1:59187/js/app.js:4:59169
 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357
 ○ e@http://127.0.0.1:59187/js/app.js:6:9402
 ○ i@http://127.0.0.1:59187/js/app.js:6:45333
 ○ http://127.0.0.1:59187/js/app.js:6:45505
 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532
 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046
 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806
 ○ f@http://127.0.0.1:59187/js/app.js:6:15887
 ○ r@http://127.0.0.1:59187/js/app.js:6:24666
 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:35
2015-03-04T00:26:30        th_a:?unnamed?          log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined)
Utilities.cpp:35
2015-03-04T00:26:34 ntp:request_time_task          request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:77
2015-03-04T00:26:34 ntp:request_time_task          request_now ] sending request to 66.175.209.17:123 ntp.cpp:81
2015-03-04T00:26:34     ntp:ntp_read_loop            read_loop ] received ntp reply from 66.175.209.17:123 ntp.cpp:147
2015-03-04T00:26:34     ntp:ntp_read_loop            read_loop ] ntp offset: -3039805, round_trip_delay 137967 ntp.cpp:161
2015-03-04T00:26:34     ntp:ntp_read_loop            read_loop ] ntp_delta_time updated to -3039805 ntp.cpp:177

Looks like backend is feeding poorly formatted json data into the GUI.
Do you have access to cli client on this machine? If you do, could you run the following commands in it and look at json output:
> eable_raw
> history xeldal2
Also do you have any estimation on how many transactions you might have for this account? It can be that there is some limit in QT's json parser implementation on a size of input data.
Thank you!


Thank you.
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 04, 2015, 06:09:40 pm

Looks like backend is feeding poorly formatted json data into the GUI.
Do you have access to cli client on this machine? If you do, could you run the following commands in it and look at json output:
> eable_raw
> history xeldal2
Also do you have any estimation on how many transactions you might have for this account? It can be that there is some limit in QT's json parser implementation on a size of input data.
Thank you!

Woah, I made the mistake of typing just "history"  it cranked out data for a good 40 minutes.

On typing "history xeldal2" I get about 41 transactions.  and the raw details go off screen and I can't access them.  Is there a way to increase the cmd screen buffer size so I can view all of it?

I can send you what i have of course , Other than a negative balance, and a memo field with this in it " ┐╢╔►╛┘t\Y²ΦìδÑ.µqu# "  I'm not seeing anything else unusual, at a glance.

The transaction with the strange memo, evidently I sent a bunch of BTS to clout-delegate1,  I don't remember doing this, but I have a terrible memory.
Title: Re: BitShares 0.6.2 Feedback
Post by: vikram on March 04, 2015, 07:19:55 pm
I can send you what i have of course , Other than a negative balance, and a memo field with this in it " ┐╢╔►╛┘t\Y²ΦìδÑ.µqu# "  I'm not seeing anything else unusual, at a glance.

The transaction with the strange memo, evidently I sent a bunch of BTS to clout-delegate1,  I don't remember doing this, but I have a terrible memory.

That strange memo could be problematic.. I am assuming that is not a real memo you wrote--looks like a memo that seemed to decrypt so it shows up but not really so it shows garbage. Maybe you can try doing "wallet_remove_transaction <transacion_id>" for that particular transaction?
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 04, 2015, 07:44:20 pm
I can send you what i have of course , Other than a negative balance, and a memo field with this in it " ┐╢╔►╛┘t\Y²ΦìδÑ.µqu# "  I'm not seeing anything else unusual, at a glance.

The transaction with the strange memo, evidently I sent a bunch of BTS to clout-delegate1,  I don't remember doing this, but I have a terrible memory.

That strange memo could be problematic.. I am assuming that is not a real memo you wrote--looks like a memo that seemed to decrypt so it shows up but not really so it shows garbage. Maybe you can try doing "wallet_remove_transaction <transacion_id>" for that particular transaction?

I will try this.  I noticed also that this transaction and every transaction before it, I can not find it on bitsharesblocks via the txID.  However, the transactions after the malformed memo show up, as do all the remaining transactions.

The malformed memo transaction was on Sept 8th 2014.

update:
remove_transaction returned{OK OK OK OK} , but the transaction is still in the history.  Gui console still cannot process history for that account.
Title: Re: BitShares 0.6.2 Feedback
Post by: liondani on March 04, 2015, 10:42:55 pm
every message burned in past on account walls was burned as an thumbs down message even we didn't had an option to choose between thumbs-up & and thumbs-down in past like we have now....
so all messages I burned that I obviously wanted to burn for a good account reputation, "did"... the opposite
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 05, 2015, 10:45:45 pm
win7x64 v0.6.2

I'm unable to send to any name with a dot in it.  Once I enter the dot the box turns red and no matter what I type next it stays red and cannot send anything.

This is a new wallet and a new account, same machine different data-dir.   At least the transaction History works on this one.   :  (

Title: Re: BitShares 0.6.2 Feedback
Post by: vikram on March 05, 2015, 11:48:01 pm
win7x64 v0.6.2

I'm unable to send to any name with a dot in it.  Once I enter the dot the box turns red and no matter what I type next it stays red and cannot send anything.

This is a new wallet and a new account, same machine different data-dir.   At least the transaction History works on this one.   :  (

Can you check for GUI update in the menu? This should have been fixed in the most recent GUI update.
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 06, 2015, 12:07:03 am
win7x64 v0.6.2

I'm unable to send to any name with a dot in it.  Once I enter the dot the box turns red and no matter what I type next it stays red and cannot send anything.

This is a new wallet and a new account, same machine different data-dir.   At least the transaction History works on this one.   :  (

Can you check for GUI update in the menu? This should have been fixed in the most recent GUI update.

"No new updates are available"

Title: Re: BitShares 0.6.2 Feedback
Post by: liondani on March 08, 2015, 07:00:41 pm
1.when I cover orders (bitEuro,bitGold) every now and then the gui client crashes immediately after the cover order confirmation, and when I restart the client the most times it offers me to reset the database or to continue... I choose to continue and it works again...

2.I shorted for example for a price of 110,560.2004 and when I tried to buy for the exactly the same price  hitting the proposed by the system ask price but the order stays open... I can only buy my shorts when I give manually a little bit bigger prices like 110,560.2005... thats very frustrating even for us, not to mention newbies they will not find out how to do it at all...
Title: Re: BitShares 0.6.2 Feedback
Post by: marcelus on March 09, 2015, 03:27:27 pm
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?
Title: Re: BitShares 0.6.2 Feedback
Post by: xeroc on March 09, 2015, 03:37:37 pm
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?
Leave the client open for some hours or so .. I guess it will catch up by that time
Title: Re: BitShares 0.6.2 Feedback
Post by: marcelus on March 09, 2015, 03:48:07 pm
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?
Leave the client open for some hours or so .. I guess it will catch up by that time

I've had it open for days buddy! Won't go past that block number.
Title: Re: BitShares 0.6.2 Feedback
Post by: xeroc on March 09, 2015, 04:43:15 pm
Dang .. in wiki.bitshares.org there a troubleshooting page .. ther you can find aomw commanda to add more peers .. that might work
Title: Re: BitShares 0.6.2 Feedback
Post by: Brekyrself on March 09, 2015, 05:37:39 pm
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?

Not sure of the file structure on OSx however to get around this on Windows you can simply delete the "chain" folder located at /User/AppData/Roaming/BitShares.  This will cause the wallet to re-sync.  As a precaution when deleting anything, backup your wallet first!
Title: Re: BitShares 0.6.2 Feedback
Post by: marcelus on March 09, 2015, 06:12:50 pm
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?

Not sure of the file structure on OSx however to get around this on Windows you can simply delete the "chain" folder located at /User/AppData/Roaming/BitShares.  This will cause the wallet to re-sync.  As a precaution when deleting anything, backup your wallet first!

I know how to do this on a mac and have a backup. Will try it now. Cheers.
Title: Re: BitShares 0.6.2 Feedback
Post by: marcelus on March 09, 2015, 06:41:33 pm
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?

Not sure of the file structure on OSx however to get around this on Windows you can simply delete the "chain" folder located at /User/AppData/Roaming/BitShares.  This will cause the wallet to re-sync.  As a precaution when deleting anything, backup your wallet first!

I know how to do this on a mac and have a backup. Will try it now. Cheers.

Worked a treat thanks. Still downloading but has gotten past that dreaded block :)
Title: Re: BitShares 0.6.2 Feedback
Post by: pc on March 10, 2015, 08:41:14 am
Yesterday one of my wallets got corrupted. It had been open + unlocked for a couple of days. When I tried shut down the client I had to kill it, apparently one thread was stuck in a loop or something. After restarting, I couldn't open the wallet anymore. The attempt fails with something about a checksum mismatch. One possible cause is that the partition where the wallet is stored became full at some point in time (but the client never gave me an error message and continued to work just fine while it was running).

Importing an old backup + regenerating keys restored my balances completely AFAICT, only the tx history shows me many UNKNOWNs in market orders.
Title: Re: BitShares 0.6.2 Feedback
Post by: xeroc on March 10, 2015, 09:07:29 am
Yesterday one of my wallets got corrupted. It had been open + unlocked for a couple of days. When I tried shut down the client I had to kill it, apparently one thread was stuck in a loop or something. After restarting, I couldn't open the wallet anymore. The attempt fails with something about a checksum mismatch. One possible cause is that the partition where the wallet is stored became full at some point in time (but the client never gave me an error message and continued to work just fine while it was running).

Importing an old backup + regenerating keys restored my balances completely AFAICT, only the tx history shows me many UNKNOWNs in market orders.
you may need to regenerate alot more keys ... there has been a change in how the market keys are derived from the account key.. those keys are regenerated only after 10500 or so ..
Title: Re: BitShares 0.6.2 Feedback
Post by: vlight on March 10, 2015, 07:36:32 pm
Sometimes when i click on BitUSD:BTS featured market it opens BitSILVER:BTS instead. (Windows 7 64 bit)
Title: Re: BitShares 0.6.2 Feedback
Post by: valzav on March 10, 2015, 09:12:28 pm
Sometimes when i click on BitUSD:BTS featured market it opens BitSILVER:BTS instead. (Windows 7 64 bit)
Did you try to upgrade to newer wallet version? As far as I remember 0.6.0 had this bug and it's definitely should be fixed in 0.6.2.
Don't forget to click Check for GUI updates in the main menu after you install it.
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 10, 2015, 11:07:03 pm
Sometimes when i click on BitUSD:BTS featured market it opens BitSILVER:BTS instead. (Windows 7 64 bit)
Did you try to upgrade to newer wallet version? As far as I remember 0.6.0 had this bug and it's definitely should be fixed in 0.6.2.
Don't forget to click Check for GUI updates in the main menu after you install it.

I still get this also.  I made a ticket about it and it was closed. https://github.com/BitShares/web_wallet/issues/632

  The issue only happens whey you click on the graph.  If you click above the graph you go to the correct market.  so not quite fixed.
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 14, 2015, 08:51:11 pm
win764
Another corrupted wallet.  I'm not able to open the wallet.  Not able to import any backups.

Code: [Select]
10001 level_map_open_failure: level_map open failure
Failure opening database: C:/Users/John/AppData/Roaming/BitShares/wallets/default
Status: Corruption: error in middle of record
    {"db":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","msg":"Corruption: error in middle of record"}
    th_a  level_map.hpp:68 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::open

    {"dir":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","create":true,"cache_size":0}
    th_a  level_map.hpp:73 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::open
Error opening wallet file C:/Users/John/AppData/Roaming/BitShares/wallets/default
    {"file":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"}
    th_a  wallet_db.cpp:186 bts::wallet::wallet_db::open
Unable to open wallet C:/Users/John/AppData/Roaming/BitShares/wallets/default
    {"wallet_file_path":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"}
    th_a  wallet.cpp:753 bts::wallet::detail::wallet_impl::open_file

    {"wallet_name":"default"}
    th_a  wallet.cpp:1075 bts::wallet::wallet::open

    {}
    th_a  common_api_client.cpp:2861 bts::rpc_stubs::common_api_client::wallet_open

    {"command":"wallet_open"}
    th_a  cli.cpp:626 bts::cli::detail::cli_impl::execute_command

Gui errors out on trying to import any backup saying "invalid password"  and crashes if you try to export.
Title: Re: BitShares 0.6.2 Feedback
Post by: vikram on March 30, 2015, 07:45:48 pm
win764
Another corrupted wallet.  I'm not able to open the wallet.  Not able to import any backups.

Code: [Select]
10001 level_map_open_failure: level_map open failure
Failure opening database: C:/Users/John/AppData/Roaming/BitShares/wallets/default
Status: Corruption: error in middle of record
    {"db":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","msg":"Corruption: error in middle of record"}
    th_a  level_map.hpp:68 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::open

    {"dir":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","create":true,"cache_size":0}
    th_a  level_map.hpp:73 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::open
Error opening wallet file C:/Users/John/AppData/Roaming/BitShares/wallets/default
    {"file":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"}
    th_a  wallet_db.cpp:186 bts::wallet::wallet_db::open
Unable to open wallet C:/Users/John/AppData/Roaming/BitShares/wallets/default
    {"wallet_file_path":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"}
    th_a  wallet.cpp:753 bts::wallet::detail::wallet_impl::open_file

    {"wallet_name":"default"}
    th_a  wallet.cpp:1075 bts::wallet::wallet::open

    {}
    th_a  common_api_client.cpp:2861 bts::rpc_stubs::common_api_client::wallet_open

    {"command":"wallet_open"}
    th_a  cli.cpp:626 bts::cli::detail::cli_impl::execute_command

Gui errors out on trying to import any backup saying "invalid password"  and crashes if you try to export.

Did you ever work this out? Possible by doing a fresh install of 0.5.3 to import the backup, and then upgrading in-place to the latest version?
Title: Re: BitShares 0.6.2 Feedback
Post by: Xeldal on March 30, 2015, 08:29:23 pm
Quote
Did you ever work this out? Possible by doing a fresh install of 0.5.3 to import the backup, and then upgrading in-place to the latest version?

Yes, that is what I did.  It worked for me.