BitShares v0.4.26 Feedback

[cn-members]

serveral problems with RC2:

1. the qt wallet still shows all blank screen:





2. unable to restore wallet backups

[liondani]

In RC2 restore wallet backup created in 0.4.24 is not working

restore wallet on v0.4.25-RC1 that was a json backup from v0.4.24.1 is not working either...  after about one minute many error messages and it starts with something like:  "unable to find key..."  ... I managed to create the same wallet only by copying the folder "wallets" and pasting it to the other server.

Sent from my ALCATEL ONE TOUCH 997D

[chsln]

In RC2 restore wallet backup created in 0.4.24 is not working

[clayop]

Keys tab does not work with delegate accounts

edit: haven't tested on RC2 because there's no windows binary yet.

[roadscape]

0.4.25-RC1
 - 'Price Limit' fields are blank on both the 'my open shorts' and 'all shorts' tables
 - 'Interest Rate' fields are blank
 - Slooow.. 0.4.24 was much faster

ninja edit:

0.4.25-RC2
 - interest rate fields are now working!
 - wallet is faster but still slow. particularly the Market page, on the initial load. (approx 15s to load)
 - Block Explorer is slow (loads after 30s)

[cryptkeeper]

when I try to open my wallet, I get an error message stating that an instance of bitshares is already running and to close it and reopen. I don't have bitshares running to my knowledge besides the one i'm trying to open. what could be the issue?

[clout]

Price limits on short orders do not work through GUI. I have not tried the CLI.

[vikram]

the scanning is so slow 
only 1 account in this wallet

Fixed: https://github.com/BitShares/bitshares/commit/33a77bd1a804335e8ea4ef76543fe461b2ff245b

Same issue with tonyk2, can't import backups. Also when I try to regenerate keys from my current wallet I get the message in second image...

Next release should let you proceed: https://github.com/BitShares/bitshares/commit/bc6fcd2fd902536640b8bde1b59794ed4caa4885

[chryspano]

Same issue with tonyk2, can't import backups. Also when I try to regenerate keys from my current wallet I get the message in second image...

(I downloaded the new wallet about 1-2 hours before and installed it after I uninstalled the 0.4.24 version)
(I still have missing bts but hope 0.4.25 or any future version will solve this)

[alt]

the scanning is so slow 
only 1 account in this wallet

Code: [Select]

  "blockchain_head_block_timestamp": "2014-12-10T03:24:50",
  "wallet_last_scanned_block_timestamp": "2014-11-13T12:13:00",
  "wallet_scan_progress": "0.71 %",


Code: [Select]

  "blockchain_head_block_timestamp": "2014-12-10T03:42:10",
  "wallet_last_scanned_block_timestamp": "2014-11-15T23:08:00",
  "wallet_scan_progress": "9.13 %",

the system cpu and the memory is enough, the process state is always  uninterruptible sleep

Code: [Select]

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                             
 9431 alt       20   0 2417664 727296 183268 D   1.0 19.4   7:34.47 bitshares_clien                                                                                     


[clayop]

Account-Key menu in GUI cannot work.

To get the key in GUI, users have to use wallet_list_my_account in console.

clayop, could you describe your issue a little bit more? Do you mean Keys tab on the account page won't? Maybe you could post a screenshot?

When I click the key on the bar, nothing happens and nothing is shown. Others don't have this problem?

[valzav]

Account-Key menu in GUI cannot work.

To get the key in GUI, users have to use wallet_list_my_account in console.

clayop, could you describe your issue a little bit more? Do you mean Keys tab on the account page won't? Maybe you could post a screenshot?

[Xeldal]

Is 0.4.25 RC1 meant to fix orphaned accounts?

I had 1 prior to update, now I have 15.

I saw your post (https://bitsharestalk.org/index.php?topic=9194.msg160105#msg160105 )--was going to wait for the final release to address it; but if you want to right now, you can try:

Code: [Select]

(wallet closed) >>> h wallet_repair_records
Usage:
wallet_repair_records [collecting_account_name]                                                       tries to repair any inconsistent wallet account, key, and transaction records
tries to repair any inconsistent wallet account, key, and transaction records

Parameters:
  collecting_account_name (account_name, optional, defaults to ""): collect any orphan balances into this account

Returns:
  void


Awesome.  That did it.  Thank you.

[vikram]

Is 0.4.25 RC1 meant to fix orphaned accounts?

I had 1 prior to update, now I have 15.

I saw your post (https://bitsharestalk.org/index.php?topic=9194.msg160105#msg160105 )--was going to wait for the final release to address it; but if you want to right now, you can try:

Code: [Select]

(wallet closed) >>> h wallet_repair_records
Usage:
wallet_repair_records [collecting_account_name]                                                       tries to repair any inconsistent wallet account, key, and transaction records
tries to repair any inconsistent wallet account, key, and transaction records

Parameters:
  collecting_account_name (account_name, optional, defaults to ""): collect any orphan balances into this account

Returns:
  void


[Xeldal]

Is 0.4.25 RC1 meant to fix orphaned accounts?

I had 1 prior to update, now I have 15.