Print Page - DevShares 0.6.2 Feedback

https://github.com/BitShares/DevShares/releases/tag/dvs%2F0.6.2

Please only use this thread to post constructive feedback that may be useful to the development team.

Keys tab bug (in delegate accounts) is still existing.

Cannot transfer to TITAN account in GUI

(http://i.imgur.com/y02XpAL.png)

Quote from: clayop on January 28, 2015, 10:47:54 pm

Cannot transfer to TITAN account in GUI

There is a bug in the GUI.
Please go to console (Account drop down/Advanced/Console) and enter the following command:
wallet_set_setting autocomplete true
Then reload the page via right click and go back to transfer, "to" field should be shown now.

(https://i.imgur.com/HEagRZt.jpg)

I get the above error if appended with " --data-dir z:\devshares"

Code: [Select]

"C:\Program Files\DevShares\bin\DevShares.exe" --data-dir z:\devshares
z: is a network drive

This worked fine in 6.1

Quote from: Xeldal on January 28, 2015, 10:58:36 pm

(https://i.imgur.com/HEagRZt.jpg)

I get the above error if appended with " --data-dir z:\devshares"
Code: [Select]
"C:\Program Files\DevShares\bin\DevShares.exe" --data-dir z:\devshares
z: is a network drive

This worked fine in 6.1

Does it work if it is a non-network drive?

Quote from: vikram on January 28, 2015, 11:13:08 pm

Quote from: Xeldal on January 28, 2015, 10:58:36 pm
(https://i.imgur.com/HEagRZt.jpg)

I get the above error if appended with " --data-dir z:\devshares"
Code: [Select]
"C:\Program Files\DevShares\bin\DevShares.exe" --data-dir z:\devshares
z: is a network drive

This worked fine in 6.1

Does it work if it is a non-network drive?

Yes, it does. I put it in C:\devshares and used

Code: [Select]

"C:\Program Files\DevShares\bin\DevShares.exe" --data-dir c:\devshares
works fine.

Win GUI:
Initially it worked fine, then I hit the back buttons a couple of times, resulting in returning to go to the login screen. After refilling my password, it froze up.
restarting resulted in an CPU and ram drain.

The only way to start it up, is to close it using task manager. And then reset database.
After syncing up, everything seems to be working fine.

Can someone explain how to get your vested balances in DVS?
I have the normal balances, and voted with the whole stack.
But trying to claim them I get 20010 insufficient funds.

请会英文的帮忙翻译：
打开钱包。输入密码，有时候要点2次解锁，才能进入钱包，
点右下角信号处，不能正确显示，有时候会小幅跳动。

Code: [Select]

default (unlocked) >>> wallet_transfer 100 DVS elmato elmato "" vote_all

4 parse_error_exception: Parse Error
Unexpected char '118' in "vote_all"
{"c":118,"s":"vote_all"}
th_a json.cpp:433 variant_from_stream
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]
{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}
th_a cli.cpp:580 parse_argument_of_known_type

{"parameter_index":5}
th_a cli.cpp:583 parse_argument_of_known_type
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]
{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]}
th_a cli.cpp:397 parse_recognized_interactive_command

{}
th_a cli.cpp:447 parse_recognized_interactive_command
Error parsing command "wallet_transfer": Parse Error (4)
Unexpected char '118' in "vote_all"
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]

Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]

Linux GUI login doesn't work with Enter key, following paste of password; it acknowledges with the timer, as if it's about to login but then falls back to the login screen.. using the mouse button Unlock works fine.

Fork?..
Network Severe delays warning with <60%.
and my delegete client is also on a 20.95 % fork too.

What is the method for getting back on the main branch?.. Is there a method for fixing a forking problem that doesn't require devs? I wondered about using eg http://dvs.bitsharesblocks.com/blocks/block?id=189535 [Previous hash] for the previous block and use that as checkpoint.. but then the website suggests that is using Client version: 0.6.1-78-g11cb6ef
Should we look to the output of list_forks to find checkpoints??

Should the client at least not stick to the main branch?.. or does it do that and we have a number of forks??

Korean(한국어) translation seems not to be imported properly.

I updated the client to 0.6.2 and now I am on a minority fork:

Code: [Select]

default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 189306,
  "blockchain_head_block_age": "2 minutes old",
  "blockchain_head_block_timestamp": "2015-01-29T10:14:00",
  "blockchain_average_delegate_participation": "12.66 %",
  "blockchain_confirmation_requirement": 303,
  "blockchain_share_supply": "2,541,653,966.76381 DVS",
  "blockchain_blocks_left_in_round": 69,
  "blockchain_next_round_time": "at least 11 minutes in the future",
  "blockchain_next_round_timestamp": "2015-01-29T10:27:00",
  "blockchain_random_seed": "8933de0235a6d4a187f7236d57f01d140f39991a",
  "client_data_dir": "/home/spartako/.DevShares_delegate",
  "client_version": "0.6.2",
  "network_num_connections": 12,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-01-29T10:15:34",
  "ntp_time_error": -0.0013990000000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-02-10T00:00:59",
  "wallet_last_scanned_block_timestamp": "2015-01-08T16:36:20",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 11 minutes in the future",
  "wallet_next_block_production_timestamp": "2015-01-29T10:30:20"
}

Quote from: spartako on January 29, 2015, 10:16:56 am

I updated the client to 0.6.2 and now I am on a minority fork:

same here, can't manage to get on the main chain... I added the problematic block to my checkpoints.json file:

Code: [Select]

[[
    1,
    "8523e28fde6eed4eb749a84e28c9c7b56870c9cc"
  ],[
    172718,
    "e452dd44902bc86110923285da03ac12e8cfbe6f"
  ],[
    173585,
    "1d1695bc8ebd3ebae0168007afb2912269adbef1"
  ],[
    179000,
    "ba3d03f5bf65d8cc051417b673206e6b0472bcae"
  ],[
    189181,
    "9c4c7f9bab5bea6a64fb1986f8ae131d9d9e2083"
  ]
]

and restarted with --resync-blockchain, but to no avail... Any suggestion as to how to do this properly? Thanks

Quote from: davidpbrown on January 29, 2015, 08:55:35 am

Linux GUI login doesn't work with Enter key, following paste of password; it acknowledges with the timer, as if it's about to login but then falls back to the login screen.. using the mouse button Unlock works fine.

Fork?..
Network Severe delays warning with <60%.
and my delegete client is also on a 20.95 % fork too.

What is the method for getting back on the main branch?.. Is there a method for fixing a forking problem that doesn't require devs? I wondered about using eg http://dvs.bitsharesblocks.com/blocks/block?id=189535 [Previous hash] for the previous block and use that as checkpoint.. but then the website suggests that is using Client version: 0.6.1-78-g11cb6ef
Should we look to the output of list_forks to find checkpoints??

Should the client at least not stick to the main branch?.. or does it do that and we have a number of forks??

have same problems.... I am stuck on 11.76% participation fork...
and I can't switch to the main chain.

1.I rebuilded
2.I resynced the blockchain
3.I deleted all folders but "wallets"
4.I repeated all of this steps several times ....

.....nothing worked like it used to be the case in the past when when I took all these steps :(

edit:
same with my seed node (185.25.22.21:2776) !!! What is worth mentioning is that I leaved yesterday the seed node on the right chain.

Quote from: wackou on January 29, 2015, 01:28:30 pm

and restarted with --resync-blockchain, but to no avail... Any suggestion as to how to do this properly? Thanks

I tried me too adding checkpoint but I am always in the minority fork.

Code: [Select]

default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 189457,
  "blockchain_head_block_age": "3 minutes old",
  "blockchain_head_block_timestamp": "2015-01-29T13:41:40",
  "blockchain_average_delegate_participation": "12.11 %",
  "blockchain_confirmation_requirement": 302,
  "blockchain_share_supply": "2,541,716,209.88472 DVS",
  "blockchain_blocks_left_in_round": 19,
  "blockchain_next_round_time": "at least 3 minutes in the future",
  "blockchain_next_round_timestamp": "2015-01-29T13:47:30",
  "blockchain_random_seed": "c67973902cf1571a893a17838c8a15ba154d65fc",
  "client_data_dir": "/home/fabiux/.DevShares_delegate",
  "client_version": "0.6.2",
  "network_num_connections": 17,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-01-29T13:44:20",
  "ntp_time_error": -0.0023600000000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "3 years 2 months in the future",
  "wallet_unlocked_until_timestamp": "2018-03-31T23:25:07",
  "wallet_last_scanned_block_timestamp": "2015-01-08T16:36:20",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 3 minutes in the future",
  "wallet_next_block_production_timestamp": "2015-01-29T13:49:00"
}

I suspect init* delegate have not upgraded to 0.6.2 and this is could be the cause of fork.

The blockchain_list_blocks command shows (on my fork) other delegates that are upgraded and no init* delegates:

Code: [Select]

HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    LATENCY PROCESSING TIME  RAND
====================================================================================================================
189457  2015-01-29T13:41:40 jcalfee1-developer-team.terrier 0       166     0       0                0000000000000000000000000000000000000000
189456  2015-01-29T13:41:30 delegate.robrigo                0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:41:20 ?                               N/A     N/A     N/A     N/A              N/A
189455  2015-01-29T13:41:10 del0.xeldal                     0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:41:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:40:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:40:40 ?                               N/A     N/A     N/A     N/A              N/A
189454  2015-01-29T13:40:30 devshares.warlock               0       166     0       0                0000000000000000000000000000000000000000
189453  2015-01-29T13:40:20 delegate-clayop                 0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:40:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:40:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:39:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:39:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:39:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:39:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:39:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:39:00 ?                               N/A     N/A     N/A     N/A              N/A
189452  2015-01-29T13:38:50 btsbreakout                     0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:38:40 ?                               N/A     N/A     N/A     N/A              N/A
189451  2015-01-29T13:38:30 bitsharesbreakout               0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:38:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:38:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:38:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:37:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:37:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:37:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:37:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:37:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:37:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:36:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:36:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:36:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:36:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:36:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:36:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:35:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:35:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:35:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:35:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:35:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:35:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:34:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:34:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:34:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:34:20 ?                               N/A     N/A     N/A     N/A              N/A
189450  2015-01-29T13:34:10 delegate.ihashfury              0       166     239     0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:34:00 ?                               N/A     N/A     N/A     N/A              N/A
189449  2015-01-29T13:33:50 emski                           0       166     259     0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:33:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:33:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:33:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:33:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:33:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:32:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:32:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:32:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:32:20 ?                               N/A     N/A     N/A     N/A              N/A
189448  2015-01-29T13:32:10 delegate.spartako               0       166     359     0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:32:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:31:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:31:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:31:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:31:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:31:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:31:00 ?                               N/A     N/A     N/A     N/A              N/A
189447  2015-01-29T13:30:50 del1.xeldal                     0       166     439     0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:30:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:30:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:30:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:30:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:30:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:29:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:29:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:29:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:29:20 ?                               N/A     N/A     N/A     N/A              N/A
189446  2015-01-29T13:29:10 del2.xeldal                     1       410     539     0                0000000000000000000000000000000000000000
MISSED  2015-01-29T13:29:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:28:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:28:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:28:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:28:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:28:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:28:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:27:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:27:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:27:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:27:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:27:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:27:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:26:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:26:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-29T13:26:30 ?                               N/A     N/A     N/A     N/A              N/A

...or the majority of the default seed nodes are on minority forks? Cold that be the reason ?

Quote from: spartako on January 29, 2015, 01:45:55 pm

I suspect init* delegate have not upgraded to 0.6.2 and this is could be the cause of fork.

The blockchain_list_blocks command shows (on my fork) other delegates that are upgraded and no init* delegates:

I made a little investigation and I am 99.9% certain you are right ! ;)
Thats why http://dvs.bitsharesblocks.com/home
says the participation % is at 84% because dev.bitsharesblocks is at Client version: 0.6.1-78-g11cb6ef
and it is there also obvious that all init delegates are on this "ex" main-chain/fork :P
So it is a fact that the minority of delegates has upgraded to the new v0.6.2

the following feedbacks are collected from the chinese community:

1. Chinese localization is still incompleted, also with lots of 'toolbar.xxx' tags
(http://i.imgur.com/HvChxvP.png)

2. in Windows client, the recipient of transaction disappeared.
(http://i.imgur.com/DwiyXQa.jpg)

3. while moving my mouse cursor to the lower right corner, there will suddenly appear one more scroll bar and change the layout
(http://i.imgur.com/y0NXtAQ.jpg)

4. no specific information while syncing (i.e., how many blocka are yet to be synced, or how many times left to complete syncing)
(http://i.imgur.com/IsUcfyL.jpg)

5. issues while unlock wallet on windows GUI: sometimes you have to enter your password and press unlock twice to unlock, sometimes it just get infinitely stucked on three running dots.
(http://i.imgur.com/IM172Nu.png)

6. the block explorer should links to http://dvs.bitsharesblocks.com, not http://bitsharesblocks.com/

Quote from: liondani on January 29, 2015, 01:58:40 pm

Quote from: spartako on January 29, 2015, 01:45:55 pm
I suspect init* delegate have not upgraded to 0.6.2 and this is could be the cause of fork.

The blockchain_list_blocks command shows (on my fork) other delegates that are upgraded and no init* delegates:

I made a little investigation and I am 99.9% certain you are right ! ;)
Thats why http://dvs.bitsharesblocks.com/home
says the participation % is at 84% because dev.bitsharesblocks is at Client version: 0.6.1-78-g11cb6ef
and it is there also obvious that all init delegates are on this "ex" main-chain/fork :P
So it is a fact that the minority of delegates has upgraded to the new v0.6.2

Great! You have found the proof of my hypothesis ;)
Waiting for init* delegates switch on our chain....

well, shouldn't a 0.6.2 with a checkpoints.json file go on the "main" chain anyway with all the init delegates? unless the fork was caused by a block that is now considered invalid by 0.6.2 but not by 0.6.1-89, I guess...

Quote from: wackou on January 29, 2015, 03:26:32 pm

well, shouldn't a 0.6.2 with a checkpoints.json file go on the "main" chain anyway with all the init delegates? unless the fork was caused by a block that is now considered invalid by 0.6.2 but not by 0.6.1-89, I guess...

I had the same thought.. main chain surely is the majority of delegates but then I think the 0.6.2 was to fix a fork; so, likely we wait. I'm surprised the init's are not upgraded, as I took those to be owned by the core dev.. surprised also they don't broadcast their versions too.

Quote from: graffenwalder on January 28, 2015, 11:52:02 pm

Win GUI:
Initially it worked fine, then I hit the back buttons a couple of times, resulting in returning to go to the login screen. After refilling my password, it froze up.
restarting resulted in an CPU and ram drain.

The only way to start it up, is to close it using task manager. And then reset database.
After syncing up, everything seems to be working fine.

Can someone explain how to get your vested balances in DVS?
I have the normal balances, and voted with the whole stack.
But trying to claim them I get 20010 insufficient funds.

What is the output of "wallet_account_vested_balances" ?

Vesting schedule in DVS was set up wrong and everything is done vesting; so if you do "wallet_collect_vesting_balances <account_name>" once, it will claim ALL of your vesting balances the first time and will just fail after that.

Quote from: wackou on January 29, 2015, 03:26:32 pm

well, shouldn't a 0.6.2 with a checkpoints.json file go on the "main" chain anyway with all the init delegates? unless the fork was caused by a block that is now considered invalid by 0.6.2 but not by 0.6.1-89, I guess...

Second fork happened because init delegate server was not upgraded and all other clients disconnected it. If client has not already switched, a resync now should get back on majority chain.

Quote from: ElMato on January 29, 2015, 05:26:12 am

Code: [Select]
default (unlocked) >>> wallet_transfer 100 DVS elmato elmato "" vote_all
4 parse_error_exception: Parse Error
Unexpected char '118' in "vote_all"
{"c":118,"s":"vote_all"}
th_a json.cpp:433 variant_from_stream
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]
{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}
th_a cli.cpp:580 parse_argument_of_known_type

{"parameter_index":5}
th_a cli.cpp:583 parse_argument_of_known_type
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]
{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]}
th_a cli.cpp:397 parse_recognized_interactive_command

{}
th_a cli.cpp:447 parse_recognized_interactive_command
Error parsing command "wallet_transfer": Parse Error (4)
Unexpected char '118' in "vote_all"
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]

Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]

Fixed. For now you can get around this by putting it in quotes like "vote_all".

Quote from: Xeldal on January 28, 2015, 10:58:36 pm

(https://i.imgur.com/HEagRZt.jpg)

I get the above error if appended with " --data-dir z:\devshares"
Code: [Select]
"C:\Program Files\DevShares\bin\DevShares.exe" --data-dir z:\devshares
z: is a network drive

This worked fine in 6.1

Unable to reproduce like this. We intermittently hang the first load of a client using a network mapped drive, but other than that it seems to work. Could there be a high delay using that drive?

Quote from: vikram on January 29, 2015, 05:10:02 pm

Quote from: graffenwalder on January 28, 2015, 11:52:02 pm
Win GUI:
Initially it worked fine, then I hit the back buttons a couple of times, resulting in returning to go to the login screen. After refilling my password, it froze up.
restarting resulted in an CPU and ram drain.

The only way to start it up, is to close it using task manager. And then reset database.
After syncing up, everything seems to be working fine.

Can someone explain how to get your vested balances in DVS?
I have the normal balances, and voted with the whole stack.
But trying to claim them I get 20010 insufficient funds.

What is the output of "wallet_account_vested_balances" ?

Vesting schedule in DVS was set up wrong and everything is done vesting; so if you do "wallet_collect_vesting_balances <account_name>" once, it will claim ALL of your vesting balances the first time and will just fail after that.

I'm pretty Sure i haven't gotten the vested balances yet. I know the exact nummer of BTS at snapshot, and it's spot on with my DVS balance.

Output:

Quote

DVS893vBuuXqA3b4nrq2MeCxxxxxxxxxxxxxxxxxxxxx",[{
"balance_id": "DVS2CAXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"sharedrop_address": "Pvw5u6QQXxxxxxxxxxxxxxxxxx",
"start_time": "2014-01-05T00:00:00",
"duration": 5184000,
"asset_id": 0,
"original_balance": 90858447,
"vested_balance": 90858447,
"claimed_balance": 0,
"available_balance": 90858447
},{
"balance_id": "DVSFHSwQdtg4vxxxxxxxxxxxxxxxx",
"sharedrop_address": "Pvw5u6QQXxxxxxxxxxxx",
"start_time": "2014-01-05T00:00:00",
"duration": 5184000,
"asset_id": 0,
"original_balance": 6670251141,
"vested_balance": 6670251141,
"claimed_balance": 0,
"available_balance": 6670251141

In total i have 23 of these sections (23 change addresses)

Edit:

I remember it didn't work in The previous version so I ran:
wallet_collect_genesis_balances <account_name>

Now looking in the recent transactions tab: it shows the balance twice as high as it should be, when I ran that command.

After voting the balance returned to where it should be without the vested balances.

I have a pic of it, but not sure how to upload it in this message.

I've had to restore wallets from backups a couple of times now on 0.6.2. The GUI-qt more clearly suggested no transactions, despite the accounts being there and all the rescans etc, didn't change that. That last event then no change by me, just a simple upgrade step from 0.6.1.

Blessed are pessimists, for they make backups!

Quote from: cn-members on January 29, 2015, 02:02:17 pm

the following feedbacks are collected from the chinese community:

The feedback I take is that the chinese community loves the bitshares Team :P

1. fuck-3i account message 8)
2. squatting toasts name 8)

(http://2.bp.blogspot.com/-MGKDLcg25M4/VMq-sLclAkI/AAAAAAAADT0/mYQeTfvyvO8/s1600/fuck3i.png)

Quote from: liondani on January 29, 2015, 11:23:11 pm

Quote from: cn-members on January 29, 2015, 02:02:17 pm
the following feedbacks are collected from the chinese community:

The feedback I take is that the chinese community loves the bitshares Team :P

1. fuck-3i account message 8)
2. squatting toasts name 8)

(http://2.bp.blogspot.com/-MGKDLcg25M4/VMq-sLclAkI/AAAAAAAADT0/mYQeTfvyvO8/s1600/fuck3i.png)

Quite true. Sometimes the more you love, the more you hate.

Expecting that init43 is now 0.6.2 (why do the inits not declare their version?), and with my client on delegate_participation: "99.02 %", I wonder this suggests z is on a fork?.. but how is that happening if both are on 0.6.2??

Code: [Select]

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         189180
     c8abe03bd24d67f1f7d0b4bac235aac3dc873201                             z              0       166 2015-01-29T07:38:40     10579     YES                  NO
     9c4c7f9bab5bea6a64fb1986f8ae131d9d9e2083                        init43              0       166 2015-01-29T07:34:50     34135     YES                 YES

GUI scrollbars are not reset to the top, whenever the user switches to and from Dashboard/Exchange etc; so, in the event they have scrolled down on one page, they might miss detail on the next page they turn to.

BitShares Forum

Other => Graveyard => DevShares => Topic started by: vikram on January 28, 2015, 10:10:12 pm