https://github.com/BitShares/bitshares/releases/tag/v0.4.25-RC1
https://github.com/BitShares/bitshares/releases/tag/v0.4.25-RC2
https://github.com/BitShares/bitshares/releases/tag/v0.4.26
Please only use this thread to post constructive feedback that may be useful to the development team.
Window version wallet occupies a lot of memory and CPU percentage, making the computer extremely slow.
flower theme can not work.
Account-Key menu in GUI cannot work.
To get the key in GUI, users have to use wallet_list_my_account in console.
if I set lockscreen to 'flowers', it actually gives me nothing but this:
(http://i.imgur.com/gTURkJk.png)
I found it's address is:
http://127.0.0.1:58770/img/logo-ico-blue.svg
but actually there is no such file
Quote from: cn-members on December 09, 2014, 07:42:02 AM
if I set lockscreen to 'flowers', it actually gives me nothing but this:
(http://i.imgur.com/gTURkJk.png)
I found it's address is:
http://127.0.0.1:58770/img/logo-ico-blue.svg
but actually there is no such file
The background should be different too, looks like those two files weren't included in the build?
Interest for shorts can not be displayed in 0.4.25 wallet .
Quote from: cn-members on December 09, 2014, 11:45:27 AM
Interest for shorts can not be displayed in 0.4.25 wallet .
What do you mean? In the ShortSell order list I see all of the interest rates as well as in my margin orders.
I think the windows build was made against a bad version of the web GUI.
Quote from: cn-members on December 09, 2014, 07:42:02 AM
if I set lockscreen to 'flowers', it actually gives me nothing but this:
I found it's address is:
http://127.0.0.1:58770/img/logo-ico-blue.svg
but actually there is no such file
I think 'flowers' theme files were not included into the gui package. Will be fixed in 0.4.25 release version.
Quote from: ripplexiaoshan on December 09, 2014, 03:46:02 AM
Window version wallet occupies a lot of memory and CPU percentage, making the computer extremely slow.
Here's what I'm seeing here while testing the Windows GUI version:
Re-indexing takes about about 10 minutes and consumes 1.38GB. If a system has less than that free memory available (after accounting for the OS and other programs), it's going to slow down dramatically as it begins paging, and this could become a very very long operation at that point.
I have sufficient memory on my system to avoid paging, so after re-indexing my cpu usage dropped to a normal 1-3% for the client. But memory stayed at 1.38GB for the duration of that session (my guess is another memory leak in the blockchain code). After restarting the client, my memory usage dropped down to the expected range (~571MB).
win7, 32 bit 0.4.25RC1
1. Connection issues - like with some older version, while working for a while suddenly and randomly fails behind.
2. Cannot import older(originally save by v.0.4.10 and v.0.4.20)/other wallet. Imported successfully just before upgrading (client old ver was 0.4.24)
(http://i.imgur.com/cihAUCW.png)
Could that have been from the bad key?
Quote from: jsidhu on December 09, 2014, 07:32:41 PM
Could that have been from the bad key?
tried 3 back ups - 2 saved by 0.4.10 and one in 0.4.20. If it matters
Quote from: cn-members on December 09, 2014, 11:45:27 AM
Interest for shorts can not be displayed in 0.4.25 wallet .
Fixed: https://github.com/BitShares/bitshares/issues/1126
Quote from: valzav on December 09, 2014, 02:52:58 PM
Quote from: cn-members on December 09, 2014, 07:42:02 AM
if I set lockscreen to 'flowers', it actually gives me nothing but this:
I found it's address is:
http://127.0.0.1:58770/img/logo-ico-blue.svg
but actually there is no such file
I think 'flowers' theme files were not included into the gui package. Will be fixed in 0.4.25 release version.
Fixed: https://github.com/BitShares/qt_wallet/commit/987d70c3e31c9da7297beec96058289ff2becf16
Quote from: tonyk2 on December 09, 2014, 07:30:22 PM
2. Cannot import older(originally save by v.0.4.10 and v.0.4.20)/other wallet. Imported successfully just before upgrading (client old ver was 0.4.24)
Fixed: https://github.com/BitShares/bitshares/commit/df0d58fd16efa3bc3c56f87e58c3abdbb6be9045
bitAsset:bitAsset markets are not working in the Windows GUI and were not working in 0.4.24 either. It's letting me submit orders, but the orders are not matching. Also, it says "insufficient feeds" at the top.
Quote from: biophil on December 09, 2014, 09:29:41 PM
bitAsset:bitAsset markets are not working in the Windows GUI and were not working in 0.4.24 either. It's letting me submit orders, but the orders are not matching. Also, it says "insufficient feeds" at the top.
This will be fixed in a future hardfork: https://github.com/BitShares/bitshares/issues/949
Is 0.4.25 RC1 meant to fix orphaned accounts?
I had 1 prior to update, now I have 15.
Quote from: Xeldal on December 09, 2014, 09:59:21 PM
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:
(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
Quote from: vikram on December 09, 2014, 10:11:58 PM
Quote from: Xeldal on December 09, 2014, 09:59:21 PM
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:
(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.
Quote from: clayop on December 09, 2014, 07:35:21 AM
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?
Quote from: valzav on December 09, 2014, 10:28:16 PM
Quote from: clayop on December 09, 2014, 07:35:21 AM
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?
the scanning is so slow :(
only 1 account in this wallet
"blockchain_head_block_timestamp": "2014-12-10T03:24:50",
"wallet_last_scanned_block_timestamp": "2014-11-13T12:13:00",
"wallet_scan_progress": "0.71 %",
"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
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
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)
(http://i.imgur.com/qVDZNwq.jpg)
(http://i.imgur.com/JjHRDZU.jpg)
Quote from: alt on December 10, 2014, 03:43:53 AM
the scanning is so slow :(
only 1 account in this wallet
Fixed: https://github.com/BitShares/bitshares/commit/33a77bd1a804335e8ea4ef76543fe461b2ff245b
Quote from: chryspano on December 10, 2014, 04:33:43 AM
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
Price limits on short orders do not work through GUI. I have not tried the CLI.
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?
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)
Keys tab does not work with delegate accounts
edit: haven't tested on RC2 because there's no windows binary yet.
In RC2 restore wallet backup created in 0.4.24 is not working
Quote from: chsln on December 11, 2014, 03:18:56 PM
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
serveral problems with RC2:
1. the qt wallet still shows all blank screen:
(http://i.imgur.com/lFGypzq.jpg)
(http://i.imgur.com/idnJmEf.jpg)
2. unable to restore wallet backups
(http://i.imgur.com/z2GJ09Z.jpg)
Can someone confirm if they still cannot import an old wallet into 0.4.26? I've put another fix in place but would like someone who previously had the problem to confirm if it works for them.
Quote from: vikram on December 12, 2014, 08:23:20 PM
Can someone confirm if they still cannot import an old wallet into 0.4.26? I've put another fix in place but would like someone who previously had the problem to confirm if it works for them.
I can with 0.4.10 backup. (could not do so with 0.4.25 RC1)
backup by - 0.4.24 RC1 - missing some funds (but have not tried anything regarding finding them aka regenerate keys or whatever) and current version 0.4.26 backup is fine (no issues).
Quote from: tonyk2 on December 12, 2014, 08:34:48 PM
Quote from: vikram on December 12, 2014, 08:23:20 PM
Can someone confirm if they still cannot import an old wallet into 0.4.26? I've put another fix in place but would like someone who previously had the problem to confirm if it works for them.
I can with 0.4.10 backup. (could not do so with 0.4.25 RC1)
backup by - 0.4.24 RC1 - missing some funds (but have not tried anything regarding finding them aka regenerate keys or whatever) and current version 0.4.26 backup is fine (no issues).
Thanks; this is exactly what I wanted to know.
We are still tracking down GUI issues; let me know what problems are present in the latest version.
(http://i.imgur.com/yMUyCpp.jpg)
transaction detail is not shown in 0.4.26
Attempts to update votes result in CPU peg and non responsiveness of thumb buttons.
Quote from: bytemaster on December 13, 2014, 11:48:21 AM
Attempts to update votes result in CPU peg and non responsiveness of thumb buttons.
Can't replicate this. Is this the thumb button on a delegate's profile or in the delegates list?
Either. Usually after sending a vote transaction.
Found minor one.
Maximum delegate pay per block is now shown. It shows "NaN.00 BTS"
I'm stuck on block 1253613. User that upgraded from .04.24
These lines appear:
--- syncing with p2p network, 22042 blocks left to fetch
--- in sync with p2p network
--- there are now 19 active connections to the p2p network
--- syncing with p2p network, 1524 blocks left to fetch
--- in sync with p2p network
--- syncing with p2p network, 583617 blocks left to fetch
--- there are now 18 active connections to the p2p network
--- in sync with p2p network
--- syncing with p2p network, 158482 blocks left to fetch
--- in sync with p2p network
--- syncing with p2p network, 9323 blocks left to fetch
--- there are now 19 active connections to the p2p network
...
This goes on and on..
I'm on the head block and delegate participation is 94.39%.
Also, since I only have 2GB in RAM, the wallet responds very slowly to commands.
I tried rescanning, resyncing, rebuilding index, resetting peer database.
Don't know what else to do..
Orders not and or matching appear only in the GUY.
(http://i.imgur.com/IJ0ONdk.png)
Both buy bitBTC were placed - the second (lower priced) is already canceled. My it is not mine after all let me check order numbers if I can. The higher priced is not but still appears only in the GUI.
Actually the supposed short is missing.(or totally messed up)
CLI output at the same time is:
>> blockchain_market_order_book BTC BTS
BIDS (* Short, + Relative, - Relative Limit) | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0.10000000 BTC 2,399.99998 BTS 0.000041666667 BTC | 0.000049427372 BTC 2,199.17962 BTS 0.10869966 BTC
0.17671190 BTC 120.42254 BTS 0.000040176778 BTC*| 0.000049438991 BTC 2,199.17979 BTS 0.10872522 BTC
0.09999999 BTC 2,493.33276 BTS 0.000040106957 BTC | 0.000050000000 BTC 2,000.00000 BTS 0.10000000 BTC
BTW, the first time I saw something similar (order not matching even with overlapping prices ) was after the delegates upgraded to 0.4.25.... hope we are not forking again.
[edit] Ohh forget it. The whole bitBTC market seems like one big mess.
Quote from: Bitcoinfan on December 13, 2014, 07:58:04 PM
I'm stuck on block 1253613. User that upgraded from .04.24
Anyone have any thoughts of how to fix this from the GUI? I've rescanned many times and have 1 or 2 connections, but it still saying catch-up.
Quote from: Bitcoinfan on December 14, 2014, 01:51:56 AM
Quote from: Bitcoinfan on December 13, 2014, 07:58:04 PM
I'm stuck on block 1253613. User that upgraded from .04.24
Anyone have any thoughts of how to fix this from the GUI? I've rescanned many times and have 1 or 2 connections, but it still saying catch-up.
Deleted the chain and peer db files and its now synced.
Any chance to reduce memory requirements for compiling on linux to something below 2gb?
Quote from: delulo on December 18, 2014, 01:47:54 AM
Any chance to reduce memory requirements for compiling on linux to something below 2gb?
I was able to compile
v0.4.27.1 for 32bit using one thread, 1.5gb of free memory and swap turned off. (ymmv obviously)