BitShares Forum
Main => General Discussion => Topic started by: vikram on April 21, 2015, 01:17:04 am
-
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.9.0-rc1
For those who are willing to help test and find any serious problems before the final release.
-
Not a serious problem. Blockchain order history in market does not show timestamp. "NaN"
-
Snappy blockchain replay. Snappy interface. Fixed my active key not being regenerated issue. Zero crashes.
Absolutely awesome. +5%
-
Right after the replay, BitShares encountered an exception. I relaunched it and got another:
Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
-
Overall slick! Here's what I found in the GUI on OSX:
Exchange page
- MPA and UIA tables are not populated
Market page
- Price graphs are not showing in 'Flipped' mode
- Price graph scrolls on its own when my cursor hovers over it
- 'Volume' and '24hr Low/High/Change' in the upper pane all read 0 but 'Latest/Call Price' is fine
- The 'Short Sell' and 'Margin Call' tables also get stuck to my cursor. The Buy/Sell tables don't seem to exhibit this behavior
Suggestions for 1280 x 800 display
- Can the price graph be shrunk vertically by 25% or so? I can't see the whole depth graph without scrolling.
- Can the Order History pane be widened a little? It requires horizontal scrolling and feels a bit cramped, especially in 'My Order History'
Also, I restarted the client and got another exception. I launched it once more and it runs fine again.
ninja edit:
I like the new graphs.. big improvement! Especially with the 'All-time' view which seems to work now! The issue I mentioned above needs to be resolved so I can get the full graph experience. Also, are tooltips in the price graph gone now, or is that a bug?
-
Torrents aren't seeded currently. Once downloaded I"ll seed all three .torrents until the next release.
-
Right after the replay, BitShares encountered an exception. I relaunched it and got another:
Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
I had a similar experience. Crashed 3-4 times then made it through the replay to the login screen.
On the login screen, unlocking the wallet causes the program to hang at the loader. Wiping the app data and resetting the chain ended in a crashing scenario like above which eventually resolves but then the hanging issue happens.
OS X isn't stable but it sounds like this release is more stable for Windows users. That's a good sign at least.
edit: let it hang logging for about 10 minutes and it eventually authed me.
-
What are we to do with the "include" folder in the .dmg?
-
edit: let it hang logging for about 10 minutes and it eventually authed me.
Looks like it's re-scaning the wallet (for transactions).
-
What are we to do with the "include" folder in the .dmg?
same question.
-
Overall slick! Here's what I found in the GUI on OSX:
Exchange page
- MPA and UIA tables are not populated
Market page
- Price graphs are not showing in 'Flipped' mode
- Price graph scrolls on its own when my cursor hovers over it
- 'Volume' and '24hr Low/High/Change' in the upper pane all read 0 but 'Latest/Call Price' is fine
- The 'Short Sell' and 'Margin Call' tables also get stuck to my cursor. The Buy/Sell tables don't seem to exhibit this behavior
Suggestions for 1280 x 800 display
- Can the price graph be shrunk vertically by 25% or so? I can't see the whole depth graph without scrolling.
- Can the Order History pane be widened a little? It requires horizontal scrolling and feels a bit cramped, especially in 'My Order History'
Also, I restarted the client and got another exception. I launched it once more and it runs fine again.
ninja edit:
I like the new graphs.. big improvement! Especially with the 'All-time' view which seems to work now! The issue I mentioned above needs to be resolved so I can get the full graph experience. Also, are tooltips in the price graph gone now, or is that a bug?
It's always surprising to see the number of bugs that just appear out of nowhere on release! :)
I'll have a look once I get home. Any values not showing are most likely related to changes in the backend client API, I only tested it with 0.8.1 and there's been some changes since.
The price graph has data for 1 year now which is why the all time view "works" as you say. The tooltip should be displayed in text inside the graph window, no moving tooltip.
You have a pretty low resolution screen but I'll have a look if there's anything to be done.
-
I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
-
I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
Can you try the "bitshares_client.exe" that is packed with the GUI executable .. it should be the CLI version and help you sync with the network
-
I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
Can you try the "bitshares_client.exe" that is packed with the GUI executable .. it should be the CLI version and help you sync with the network
Where do I find that?
-
Where do I find that?
Is it not in the install path? I am not sure it's packed with the GUI :/
-
git checkout bts/0.9.0-rc1
make forcebuildweb
The source directory
/source/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
Am I missing something?
-
git checkout bts/0.9.0-rc1
make forcebuildweb
The source directory
/source/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
Am I missing something?
git submodule update --init --recursivewill fix this
-
Any particular reason for the seemly arbitrary renaming of members inside the JSON returned by get_asset?
issuer_account_id -> issuer_id
current_share_supply -> current_supply
maximum_share_supply -> max_supply
etc?
-
No way to do titan anymore?
-
git submodule update --init --recursivewill fix this
Thanks xeroc!
-
{\"jsonrpc\":\"2\",\"id\":1,\"method\":\"wallet_transfer\",\"params\":[\"0.0242\",\"USD\",\"gatewaytest\",\"gatewayclient\",\"mX: buy USD\",\"vote_recommended\"]}
Results in this error:
result "{\"id\":1,\"error\":{\"message\":\"duplicate account name (20025)\\n\\n\\n\\n\\n\\n\",\"detail\":\"20025 duplicate_account_name: duplicate account name\\n\\n {\\\"*recipient_account\\\":{\\\"index\\\":190,\\\"id\\\":0,\\\"name\\\":\\\"gatewayclient\\\",\\\"public_data\\\":null,\\\"owner_key\\\":\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\",\\\"active_key_history\\\":[[\\\"2015-01-12T08:58:01\\\",\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\"]],\\\"registration_date\\\":\\\"1970-01-01T00:00:00\\\",\\\"last_update\\\":\\\"2015-01-12T08:58:01\\\",\\\"last_child_key_index\\\":0,\\\"block_production_enabled\\\":false,\\\"custom_data\\\":{},\\\"approved\\\":0},\\\"*registered_recipient_account\\\":{\\\"id\\\":32380,\\\"name\\\":\\\"gatewayclient\\\",\\\"public_data\\\":null,\\\"owner_key\\\":\\\"BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq\\\",\\\"active_key_history\\\":[[\\\"2015-01-14T08:45:50\\\",\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\"],[\\\"2015-01-15T20:53:00\\\",\\\"BTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H\\\"]],\\\"registration_date\\\":\\\"2015-01-14T08:45:50\\\",\\\"last_update\\\":\\\"2015-01-15T20:53:00\\\",\\\"meta_data\\\":{\\\"type\\\":\\\"titan_account\\\",\\\"data\\\":\\\"\\\"}}}\\n th_a wallet.cpp:146 bts::wallet::detail::wallet_impl::deposit_from_transaction\\n\\n {\\\"transaction\\\":{\\\"expiration\\\":\\\"2015-04-21T15:37:43\\\",\\\"operations\\\":[{\\\"type\\\":\\\"withdraw_op_type\\\",\\\"data\\\":{\\\"balance_id\\\":\\\"BTS2omvvwP4A5cpxmT9K9WCm4YpaSewDaXXA\\\",\\\"amount\\\":13,\\\"claim_input_data\\\":\\\"\\\"}},{\\\"type\\\":\\\"withdraw_op_type\\\",\\\"data\\\":{\\\"balance_id\\\":\\\"BTSEUzXxEeuKR6eLTWBexdQqcnRxG6XVeBo7\\\",\\\"amount\\\":242,\\\"claim_input_data\\\":\\\"\\\"}}],\\\"signatures\\\":[]},\\\"amount\\\":{\\\"amount\\\":242,\\\"asset_id\\\":22},\\\"sender\\\":{\\\"index\\\":128,\\\"id\\\":32192,\\\"name\\\":\\\"gatewaytest\\\",\\\"public_data\\\":{\\\"gui_data\\\":{\\\"website\\\":\\\"\\\"}},\\\"owner_key\\\":\\\"BTS5dvyrpghWB9vmcZtcJVWJtYhLCQ4S8ptriskuLv45Qqi4FDe8X\\\",\\\"active_key_history\\\":[[\\\"2015-01-09T16:26:50\\\",\\\"BTS8mxPVLbNLbVqiy9Lk3woFdtFU6xzhMJhY4NRbyE3YuNJUL85YF\\\"],[\\\"2015-01-17T19:52:30\\\",\\\"BTS5SekcLhriLeAhtLrnNhoBjy4tqSgacgnWm95WB5x28sau1DsoX\\\"]],\\\"registration_date\\\":\\\"2015-01-09T16:26:50\\\",\\\"last_update\\\":\\\"2015-01-17T19:52:30\\\",\\\"meta_data\\\":{\\\"type\\\":\\\"titan_account\\\",\\\"data\\\":\\\"\\\"},\\\"last_child_key_index\\\":0,\\\"block_production_enabled\\\":false,\\\"custom_data\\\":{},\\\"approved\\\":0},\\\"recipient\\\":{\\\"index\\\":2256,\\\"contact_type\\\":\\\"account_name\\\",\\\"data\\\":\\\"gatewayclient\\\",\\\"label\\\":\\\"gatewayclient\\\",\\\"custom_data\\\":{}},\\\"memo\\\":\\\"mX: buy USD\\\"}\\n th_a wallet.cpp:204 bts::wallet::detail::wallet_impl::deposit_from_transaction\\n\\n {\\\"amount\\\":{\\\"amount\\\":242,\\\"asset_id\\\":22},\\\"sender_account_name\\\":\\\"gatewaytest\\\",\\\"generic_recipient\\\":\\\"gatewayclient\\\",\\\"memo\\\":\\\"mX: buy USD\\\",\\\"strategy\\\":\\\"vote_recommended\\\",\\\"sign\\\":true}\\n th_a wallet.cpp:2830 bts::wallet::wallet::transfer\\n\\n {\\\"amount_to_transfer\\\":\\\"0.0242\\\",\\\"asset_symbol\\\":\\\"USD\\\",\\\"from_account_name\\\":\\\"gatewaytest\\\",\\\"recipient\\\":\\\"gatewayclient\\\",\\\"memo_message\\\":\\\"mX: buy USD\\\",\\\"strategy\\\":\\\"vote_recommended\\\"}\\n th_a wallet_api.cpp:322 bts::client::detail::client_impl::wallet_transfer\\n\\n {}\\n th_a common_api_client.cpp:3845 bts::rpc_stubs::common_api_client::wallet_transfer\",\"code\":20025}}" string
This used to work in the previous version - it's a simple USD transfer from gatewaytest to gatewayclient.
-
What are we to do with the "include" folder in the .dmg?
Ignore it.
-
Right after the replay, BitShares encountered an exception. I relaunched it and got another:
Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
I had a similar experience. Crashed 3-4 times then made it through the replay to the login screen.
On the login screen, unlocking the wallet causes the program to hang at the loader. Wiping the app data and resetting the chain ended in a crashing scenario like above which eventually resolves but then the hanging issue happens.
OS X isn't stable but it sounds like this release is more stable for Windows users. That's a good sign at least.
edit: let it hang logging for about 10 minutes and it eventually authed me.
Wallet database will upgrade once on first open and can take some time--I've added a note to the changelog.
-
Any particular reason for the seemly arbitrary renaming of members inside the JSON returned by get_asset?
issuer_account_id -> issuer_id
current_share_supply -> current_supply
maximum_share_supply -> max_supply
etc?
Sorry, I've added a note about this in the API changes.
No real external reason for these particular renames. I believe I was renaming them to force compiler errors at all usages while I was writing the advanced UIA code.
-
{\"jsonrpc\":\"2\",\"id\":1,\"method\":\"wallet_transfer\",\"params\":[\"0.0242\",\"USD\",\"gatewaytest\",\"gatewayclient\",\"mX: buy USD\",\"vote_recommended\"]}
Results in this error:
result "{\"id\":1,\"error\":{\"message\":\"duplicate account name (20025)\\n\\n\\n\\n\\n\\n\",\"detail\":\"20025 duplicate_account_name: duplicate account name\\n\\n {\\\"*recipient_account\\\":{\\\"index\\\":190,\\\"id\\\":0,\\\"name\\\":\\\"gatewayclient\\\",\\\"public_data\\\":null,\\\"owner_key\\\":\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\",\\\"active_key_history\\\":[[\\\"2015-01-12T08:58:01\\\",\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\"]],\\\"registration_date\\\":\\\"1970-01-01T00:00:00\\\",\\\"last_update\\\":\\\"2015-01-12T08:58:01\\\",\\\"last_child_key_index\\\":0,\\\"block_production_enabled\\\":false,\\\"custom_data\\\":{},\\\"approved\\\":0},\\\"*registered_recipient_account\\\":{\\\"id\\\":32380,\\\"name\\\":\\\"gatewayclient\\\",\\\"public_data\\\":null,\\\"owner_key\\\":\\\"BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq\\\",\\\"active_key_history\\\":[[\\\"2015-01-14T08:45:50\\\",\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\"],[\\\"2015-01-15T20:53:00\\\",\\\"BTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H\\\"]],\\\"registration_date\\\":\\\"2015-01-14T08:45:50\\\",\\\"last_update\\\":\\\"2015-01-15T20:53:00\\\",\\\"meta_data\\\":{\\\"type\\\":\\\"titan_account\\\",\\\"data\\\":\\\"\\\"}}}\\n th_a wallet.cpp:146 bts::wallet::detail::wallet_impl::deposit_from_transaction\\n\\n {\\\"transaction\\\":{\\\"expiration\\\":\\\"2015-04-21T15:37:43\\\",\\\"operations\\\":[{\\\"type\\\":\\\"withdraw_op_type\\\",\\\"data\\\":{\\\"balance_id\\\":\\\"BTS2omvvwP4A5cpxmT9K9WCm4YpaSewDaXXA\\\",\\\"amount\\\":13,\\\"claim_input_data\\\":\\\"\\\"}},{\\\"type\\\":\\\"withdraw_op_type\\\",\\\"data\\\":{\\\"balance_id\\\":\\\"BTSEUzXxEeuKR6eLTWBexdQqcnRxG6XVeBo7\\\",\\\"amount\\\":242,\\\"claim_input_data\\\":\\\"\\\"}}],\\\"signatures\\\":[]},\\\"amount\\\":{\\\"amount\\\":242,\\\"asset_id\\\":22},\\\"sender\\\":{\\\"index\\\":128,\\\"id\\\":32192,\\\"name\\\":\\\"gatewaytest\\\",\\\"public_data\\\":{\\\"gui_data\\\":{\\\"website\\\":\\\"\\\"}},\\\"owner_key\\\":\\\"BTS5dvyrpghWB9vmcZtcJVWJtYhLCQ4S8ptriskuLv45Qqi4FDe8X\\\",\\\"active_key_history\\\":[[\\\"2015-01-09T16:26:50\\\",\\\"BTS8mxPVLbNLbVqiy9Lk3woFdtFU6xzhMJhY4NRbyE3YuNJUL85YF\\\"],[\\\"2015-01-17T19:52:30\\\",\\\"BTS5SekcLhriLeAhtLrnNhoBjy4tqSgacgnWm95WB5x28sau1DsoX\\\"]],\\\"registration_date\\\":\\\"2015-01-09T16:26:50\\\",\\\"last_update\\\":\\\"2015-01-17T19:52:30\\\",\\\"meta_data\\\":{\\\"type\\\":\\\"titan_account\\\",\\\"data\\\":\\\"\\\"},\\\"last_child_key_index\\\":0,\\\"block_production_enabled\\\":false,\\\"custom_data\\\":{},\\\"approved\\\":0},\\\"recipient\\\":{\\\"index\\\":2256,\\\"contact_type\\\":\\\"account_name\\\",\\\"data\\\":\\\"gatewayclient\\\",\\\"label\\\":\\\"gatewayclient\\\",\\\"custom_data\\\":{}},\\\"memo\\\":\\\"mX: buy USD\\\"}\\n th_a wallet.cpp:204 bts::wallet::detail::wallet_impl::deposit_from_transaction\\n\\n {\\\"amount\\\":{\\\"amount\\\":242,\\\"asset_id\\\":22},\\\"sender_account_name\\\":\\\"gatewaytest\\\",\\\"generic_recipient\\\":\\\"gatewayclient\\\",\\\"memo\\\":\\\"mX: buy USD\\\",\\\"strategy\\\":\\\"vote_recommended\\\",\\\"sign\\\":true}\\n th_a wallet.cpp:2830 bts::wallet::wallet::transfer\\n\\n {\\\"amount_to_transfer\\\":\\\"0.0242\\\",\\\"asset_symbol\\\":\\\"USD\\\",\\\"from_account_name\\\":\\\"gatewaytest\\\",\\\"recipient\\\":\\\"gatewayclient\\\",\\\"memo_message\\\":\\\"mX: buy USD\\\",\\\"strategy\\\":\\\"vote_recommended\\\"}\\n th_a wallet_api.cpp:322 bts::client::detail::client_impl::wallet_transfer\\n\\n {}\\n th_a common_api_client.cpp:3845 bts::rpc_stubs::common_api_client::wallet_transfer\",\"code\":20025}}" string
This used to work in the previous version - it's a simple USD transfer from gatewaytest to gatewayclient.
It looks like you have a local account or contact in your wallet named gatewayclient with different keys compared to the gatewayclient registered on the blockchain. You might have to use `wallet_account_rename` or `wallet_add_contact` to rename the local entry.
-
Well 0.9.0 is replaying the blockchain for the last 20 minutes (at 65% now). I had hoped the db changes would alleviate this.
-
It looks like you have a local account or contact in your wallet named gatewayclient with different keys compared to the gatewayclient registered on the blockchain. You might have to use `wallet_account_rename` or `wallet_add_contact` to rename the local entry.
Hmmm, that's very odd. I do appear to have an unregistered account with that name, but I cannot rename it:
default (unlocked) >>> wallet_rename_account gatewayclient oisdjfosfjsf
20032 key_already_registered: key belongs to other account
or retract it:
default (unlocked) >>> wallet_account_retract gatewayclient monsterer
20025 duplicate_account_name: duplicate account name
{"*local_account":{"index":190,"id":0,"name":"gatewayclient","public_data":null,"owner_key":"BTS
6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB","active_key_history":[["2015-01-12T08:58:01","BT
S6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB"]],"registration_date":"1970-01-01T00:00:00","la
st_update":"2015-01-12T08:58:01","last_child_key_index":0,"block_production_enabled":false,"custom_d
ata":{},"approved":0},"*chain_account":{"id":32380,"name":"gatewayclient","public_data":null,"owner_
key":"BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq","active_key_history":[["2015-01-14T08:4
5:50","BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB"],["2015-01-15T20:53:00","BTS5zU8LZUVPT
DV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H"]],"registration_date":"2015-01-14T08:45:50","last_update":
"2015-01-15T20:53:00","meta_data":{"type":"titan_account","data":""}}}
th_a wallet.cpp:1332 bts::wallet::wallet::get_account
{"account_name":"gatewayclient"}
th_a wallet.cpp:1345 bts::wallet::wallet::get_account
{"account_to_retract":"gatewayclient","pay_from_account":"monsterer","sign":true}
th_a wallet.cpp:3451 bts::wallet::wallet::retract_account
{}
th_a common_api_client.cpp:6310 bts::rpc_stubs::common_api_client::wallet_account_retract
{"command":"wallet_account_retract"}
th_a cli.cpp:626 bts::cli::detail::cli_impl::execute_command
What can I do?
-
$ ./bitshares_client --server
Loading blockchain from: /home/delegate/.BitShares/chain
Loading config from file: /home/delegate/.BitShares/config.json
Using built-in blockchain checkpoints
Initializing state from built-in genesis file
Please be patient, this will take several minutes...
Successfully replayed 2338510 blocks in 9613 seconds.
Blockchain size changed from 1309MiB to 1307MiB.
Starting JSON RPC server on port 9988
Starting HTTP JSON RPC server on port 19988
Attempting to map P2P port 1700 with UPNP...
(wallet closed) >>> Segmentation fault
Restarting seems to have fixed this ... daemon runnning now
-
It looks like you have a local account or contact in your wallet named gatewayclient with different keys compared to the gatewayclient registered on the blockchain. You might have to use `wallet_account_rename` or `wallet_add_contact` to rename the local entry.
Hmmm, that's very odd. I do appear to have an unregistered account with that name, but I cannot rename it:
default (unlocked) >>> wallet_rename_account gatewayclient oisdjfosfjsf
20032 key_already_registered: key belongs to other account
or retract it:
default (unlocked) >>> wallet_account_retract gatewayclient monsterer
20025 duplicate_account_name: duplicate account name
{"*local_account":{"index":190,"id":0,"name":"gatewayclient","public_data":null,"owner_key":"BTS
6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB","active_key_history":[["2015-01-12T08:58:01","BT
S6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB"]],"registration_date":"1970-01-01T00:00:00","la
st_update":"2015-01-12T08:58:01","last_child_key_index":0,"block_production_enabled":false,"custom_d
ata":{},"approved":0},"*chain_account":{"id":32380,"name":"gatewayclient","public_data":null,"owner_
key":"BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq","active_key_history":[["2015-01-14T08:4
5:50","BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB"],["2015-01-15T20:53:00","BTS5zU8LZUVPT
DV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H"]],"registration_date":"2015-01-14T08:45:50","last_update":
"2015-01-15T20:53:00","meta_data":{"type":"titan_account","data":""}}}
th_a wallet.cpp:1332 bts::wallet::wallet::get_account
{"account_name":"gatewayclient"}
th_a wallet.cpp:1345 bts::wallet::wallet::get_account
{"account_to_retract":"gatewayclient","pay_from_account":"monsterer","sign":true}
th_a wallet.cpp:3451 bts::wallet::wallet::retract_account
{}
th_a common_api_client.cpp:6310 bts::rpc_stubs::common_api_client::wallet_account_retract
{"command":"wallet_account_retract"}
th_a cli.cpp:626 bts::cli::detail::cli_impl::execute_command
What can I do?
Hmm actually looking closer, it looks like the same account, but your local version looks like:
owner_key: BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
active_keys:
BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
showing up as unregistered
And the blockchain version looks like:
owner_key: BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq
active_keys:
BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
BTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H
Do you have the private key for BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq ?
Can you try "scan 0 1" and see if your local account gets updated to be consistent with the blockchain?
-
Hmm actually looking closer, it looks like the same account, but your local version looks like:
owner_key: BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
active_keys:
BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
showing up as unregistered
And the blockchain version looks like:
owner_key: BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq
active_keys:
BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
BTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H
Not sure if this helps, but I can recall that initially, the active_keys have
been indentical to the owner key. Don't know which version changed that.
@monsterer .. have you imported that key to the wallet or have you created it within the wallet?
-
I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
This sounds like a possible side-effect of the wallet db upgrade on first open--has your situation changed at all?
-
just sent some NEWBIE UIA. however, the popup said I received 0.1 BTS (fee) instead of NEWBIE Amount.
Edit: also got some new accounts in my wallet. some newbies I tried to help - I'd like to see a function to delete unused names
-
win7x64, i7, 16G RAM, SSD
1.) >Transfer>Address Book> shows about 20 unregistered full (ex:"BTS8cfTrNpPt3....") addresses as well as about 20 seemingly random delegate names that I certainly never added and never made transfers with. Also every name in this list, is listed as "unregistered" with the only exceptions being my own account names.
2.) Under Recent Transactions on dashboard and under every individual account; still "There are no transactions!" (for me anyways, there is a record with special characters in the memo that I believe may be causing this.error: Unterminated string)
3.) >Delegates>My Votes> My votes seem to have been reset to only vote for delegates in my wallet. None of my other votes are present
EDIT: I sent a transfer and it looks like all the votes are still there. They are just not displayed in GUI.
4.) >Exchange>%market> Wallet occasionally crashes on selecting a market
5.) >Exchange>%market> Margin Orders and Short Orders Button produce new tables underneath Buy and sell tables. Not sure if this is the intended function.
- Lots of dead white space in the Buy and Sell Tables. They could be joined in 1 table and use half the current space.
- Lots of dead white space everywhere else too. I hope we are not catering to 800 x 600 res. Can we not use relative sizing like with CSS em's?
- I have lots of personal gripes about the layout but they are not really bugs and it may just be me, so I probably shouldn't list them here. Hoping at some point we can just import Themes or layouts made by other users.
- The chart: Without period adjustments (one candles time frame), having indicators is fairly useless. mouse wheel zoom would be nice too. Really any indicators we support should have their own adjustments as well. Many traders use different and very particular settings. If we intend to change out from using "high-charts" its not worth worry about all this just yet, of course. Perhaps this wallet should not be geared towards serious traders anyway?
-
just sent some NEWBIE UIA. however, the popup said I received 0.1 BTS (fee) instead of NEWBIE Amount.
Edit: also got some new accounts in my wallet. some newbies I tried to help - I'd like to see a function to delete unused names
The accounts that do not belong to you are a bug due to a change in how the client works, we should be able to sort that one out with a GUI update.
-
Not sure if this helps, but I can recall that initially, the active_keys have
been indentical to the owner key. Don't know which version changed that.
@monsterer .. have you imported that key to the wallet or have you created it within the wallet?
It's more likely that I added it as a contact account initially, and then registered it later on the other wallet. I can't rightly remember, tho. I don't think I imported the private keys.
edit: However... when I upgraded to 0.9.0-RC1 and opened the wallet, the local wallet here did a 'repairing wallet' operation, or something similar sounding to that. Perhaps that was a factor.
edit2: of course, adding a contact of an unregistered account would have meant I would have had to import public keys, wouldn't it?
-
Here's another bug: UIA balances (in the GUI) don't update correctly after you do a send.
If you issue some UIA from an account in wallet A to wallet B and then send some UIA back from B to A, then balance in B never updates to reflect the send.
edit: It's just a display bug in the GUI, the balances are fine when you call wallet_account_balance
-
For unknown reasons, I cannot create a UIA(NOTE) sell order. (on GUI)
getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_bid@app.js:46:7599
○ post_ask@app.js:43:48237
○ app.js:43:46411
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"0.305000000000","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"0.305000000000","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"0.305000000000"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"0.305000000000","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"0.305000000000","quantity_symbol":"BTS","quote_price":"3.278688524590","quote_symbol":"NOTE","sign":true}
bitshares wallet.cpp:3549 bts::wallet::wallet::submit_bid
{}
bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
-
Does "wallet_publish_price_feed" require a float/double price or a satoshi/larimer?
-
Does "wallet_publish_price_feed" require a float/double price or a satoshi/larimer?
All decimal amounts/prices should be input as strings now.
-
1. in the internal market page, the timestamp of trading history is not shown:
(http://i.imgur.com/xJa8m50.png)
2. Sometimes in your account page, there would be acoount of others listed. While surely (or sadly) you cannot spend money of those acoounts, this situation is kind of bothering.
-
Im not able to place a short. I get "Invalid asset amount(35005)" and then "JSON parse error: unterminated string"
getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_short@app.js:46:7953
○ post_short@app.js:43:47902
○ app.js:43:46465
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"2173.562540000000","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"2173.562540000000","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"2173.562540000000"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"2173.562540000000","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"enki","real_quantity_xts":"2173.562540000000","quote_symbol":"USD","apr":"0","collateral_symbol":"BTS","price_limit":"0.004600740811","sign":true}
bitshares wallet.cpp:3610 bts::wallet::wallet::submit_short
{}
bitshares common_api_client.cpp:5347 bts::rpc_stubs::common_api_client::wallet_market_submit_short
Also, after confirming an order, the order often disappears from the UI and gives no indication of whether the order was made, canceled, lost, pending, complete, ? etc., it shows nothing , and often takes 2 or 3 minutes for the order to show on the books. And then other times its near instant. I noticed this in prior versions primarily with short orders. I'm not able to test it now because Im not able to short at all.
Several times because of this I've placed the same order twice thinking it just got lost or errored out.
-
Does "wallet_publish_price_feed" require a float/double price or a satoshi/larimer?
All decimal amounts/prices should be input as strings now.
ok .. just fixed my feed script ..
-
1.) >Exchange> Market-Pegged Assets tab and User-Issued Assets tab are both empty
2.) There is a market BTC:USD and bitBTC:bitUSD they appear to be the same book with same history etc, just different names?
but, there's also a bitBTC:USD and bitUSD:BTC markets with no book and no history. I don't get it.
3.) >Exchange>%market> Buy tab - "Lowest Ask xxx.xxxxx" doesn't includes short orders for lowest Ask.
Suggestion:
4.) >Exchange>%market> - get rid of 24hr Low, 24hr High, and Volume. Ideally this information can be taken from the chart. One would simply change the chart period to 1 day (every candle = 24 hours)(I understand we don't currently have period selection) and hover over the 24hour period you are interested in and this information would be displayed. Also I think the constant repetition of (BTS/bitUSD)(bitUSD)(BTS/bitUSD)(BTS/bitUSD)(BTS/bitUSD)(BTS/bitUSD)(BTS/bitUSD) in most cases is not necessary. All one needs to do is look at the BASE in the pair your trading (ex: BASE:QUOTE) and you should know what every number is representative of. Its fine in some places but gets very redundant and just takes up space. Get rid of these and you can make the actually information, the numbers, much bigger and readable without squinting.
-
Ubuntu 64bit cli version.
Seems to crash after an hour or two, need to keep restarting when this happens.
The only message there is "killed".
This was on a fresh account that never had a previous version of bitshares before.
Deleting .Bitshares folder just results in everything starting over again.
Command line is extremely slow to respond and this slowness grows the longer the client is running.
Command line slowness is no joke, there is always literally at least 1 second in between characters, regardless of my typing speed.
I think you have a memory leak because the whole machine slowed to a crawl near the end of the last incident then became snappy again once the "killed" message appeared.
Have not yet synced the block chain, been at it 2 days.
Thanks for the hard work though!
-
Ubuntu 64bit cli version.
Seems to crash after an hour or two, need to keep restarting when this happens.
The only message there is "killed".
This was on a fresh account that never had a previous version of bitshares before.
Deleting .Bitshares folder just results in everything starting over again.
Command line is extremely slow to respond and this slowness grows the longer the client is running.
Command line slowness is no joke, there is always literally at least 1 second in between characters, regardless of my typing speed.
I think you have a memory leak because the whole machine slowed to a crawl near the end of the last incident then became snappy again once the "killed" message appeared.
Have not yet synced the block chain, been at it 2 days.
Thanks for the hard work though!
you OS kills the client if it neess more ram than you have ..
Also, search the bts.wiki for "chain servers" .. it will show you how to sync alot faster!
-
Ubuntu 64bit cli version.
Seems to crash after an hour or two, need to keep restarting when this happens.
The only message there is "killed".
This was on a fresh account that never had a previous version of bitshares before.
Deleting .Bitshares folder just results in everything starting over again.
Command line is extremely slow to respond and this slowness grows the longer the client is running.
Command line slowness is no joke, there is always literally at least 1 second in between characters, regardless of my typing speed.
I think you have a memory leak because the whole machine slowed to a crawl near the end of the last incident then became snappy again once the "killed" message appeared.
Have not yet synced the block chain, been at it 2 days.
Thanks for the hard work though!
How much memory have you?
Are your system using a swap file?
-
It took me 4 hours to re-index on my non-SSD machine with --statistics-enabled, and 8770 seconds with no --statistics-enabled. Heavy IO operations.
-
No way to do titan anymore?
TITAN is possible with CLI/console.
-
Overall slick! Here's what I found in the GUI on OSX:
Exchange page
- MPA and UIA tables are not populated
Market page
- Price graphs are not showing in 'Flipped' mode
- Price graph scrolls on its own when my cursor hovers over it
- 'Volume' and '24hr Low/High/Change' in the upper pane all read 0 but 'Latest/Call Price' is fine
- The 'Short Sell' and 'Margin Call' tables also get stuck to my cursor. The Buy/Sell tables don't seem to exhibit this behavior
Suggestions for 1280 x 800 display
- Can the price graph be shrunk vertically by 25% or so? I can't see the whole depth graph without scrolling.
- Can the Order History pane be widened a little? It requires horizontal scrolling and feels a bit cramped, especially in 'My Order History'
Also, I restarted the client and got another exception. I launched it once more and it runs fine again.
ninja edit:
I like the new graphs.. big improvement! Especially with the 'All-time' view which seems to work now! The issue I mentioned above needs to be resolved so I can get the full graph experience. Also, are tooltips in the price graph gone now, or is that a bug?
It's always surprising to see the number of bugs that just appear out of nowhere on release! :)
I'll have a look once I get home. Any values not showing are most likely related to changes in the backend client API, I only tested it with 0.8.1 and there's been some changes since.
The price graph has data for 1 year now which is why the all time view "works" as you say. The tooltip should be displayed in text inside the graph window, no moving tooltip.
You have a pretty low resolution screen but I'll have a look if there's anything to be done.
The 0 numbers issue could caused by the API change "all numbers return as strings"
-
I wasn't able to create a short earlier. The only way I can get it to go through is if the collateral field does not contain a decimal.
-
4.) >Exchange>%market> Wallet occasionally crashes on selecting a market
There have been reports of this for a long time, but we haven't been able to track it down yet: https://github.com/BitShares/bitshares/issues/1477
It would be extremely helpful if anyone could get a stack trace of this crash.
-
I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
This sounds like a possible side-effect of the wallet db upgrade on first open--has your situation changed at all?
Final release should have a fix for the extraneous accounts showing up.
-
I wasn't able to create a short earlier. The only way I can get it to go through is if the collateral field does not contain a decimal.
Maybe this is caused by the API change "all numbers should be passed in as strings" as well.
@svk31
-
4.) >Exchange>%market> Wallet occasionally crashes on selecting a market
There have been reports of this for a long time, but we haven't been able to track it down yet: https://github.com/BitShares/bitshares/issues/1477
It would be extremely helpful if anyone could get a stack trace of this crash.
Yes it does it and it is indeed randomly ,from what I can tell ( in 0.8.0).
The only relatively sure [7-8 out of 10 times on 8G + regular hard drive] way to achieve/recreate it is:
- Restart the client (GUI) after at least 6h of not running it. (preferably 24h+)
- Go to exchange; and click on non-BTS market (so something like bitUSD:bitBTC should work) do this fast - before the Market (i.e. its graphs) has fully loaded.
[edit] And no I have not let it to do crush as of late - it starts consuming memory like crazy in a matter of minutes. So I kill the process when it approaches 2G RAM.
-
4.) >Exchange>%market> Wallet occasionally crashes on selecting a market
There have been reports of this for a long time, but we haven't been able to track it down yet: https://github.com/BitShares/bitshares/issues/1477
It would be extremely helpful if anyone could get a stack trace of this crash.
Yes it does it and it is indeed randomly ,from what I can tell ( in 0.8.0).
The only relatively sure [7-8 out of 10 times on 8G + regular hard drive] way to achieve/recreate it is:
- Restart the client (GUI) after at least 6h of not running it. (preferably 24h+)
- Go to exchange; and click on non-BTS market (so something like bitUSD:bitBTC should work) do this fast - before the Market (i.e. its graphs) has fully loaded.
[edit] And no I have not let it to do crush as of late - it starts consuming memory like crazy in a matter of minutes. So I kill the process when it approaches 2G RAM.
Your issue is probably caused by the poor performance while fetching historical (matched) market orders especially in non-BTS market. See https://github.com/BitShares/bitshares/issues/1202.
And perhaps there are race conditions somewhere...
-
Possible memory leak while 'Repairing key record'.
I was running the client with a max_memory limit, it crashed:
Continuing wallet upgrade...
Repairing key record 11746MEM CPU 555.43 MEM 4814328 MAXMEM 4814328 STALE 1721
-
QT wallet is crashing for me. Here's the console log after it did it's block replay. Re-running the program causes the same exception apart from the initial "successfully replayed / blockchain size changed" lines.
Loading config from file: /home/chris/.BitShares/config.json
Using built-in blockchain checkpoints
Initializing state from built-in genesis file
Successfully replayed 2342769 blocks in 1840 seconds.
Blockchain size changed from 1308MiB to 1310MiB.
/index.html
/css/app.css
/js/app.js
/locale-en.json
/img/xts-logo-xl-white-shadow.png
/img/logo-ico.svg
/img/xt-background.jpg
/webfonts/Roboto-Regular-webfont.woff
/webfonts/fontawesome-webfont.woff
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
/webfonts/Roboto-Regular-webfont.ttf
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
/webfonts/Roboto-Regular-webfont.svg
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
fish: Job 1, “./programs/qt_wallet/bin/BitShares ” terminated by signal SIGSEGV (Address boundary error)
-
Getting "invalid asset amount (35005)" when attempting to short bitUSD
getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_short@app.js:46:7953
○ post_short@app.js:43:47902
○ app.js:43:46465
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"430068.550050000020","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"430068.550050000020","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"430068.550050000020"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"430068.550050000020","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"mattjohnson","real_quantity_xts":"430068.550050000020","quote_symbol":"USD","apr":"0.100000000000","collateral_symbol":"BTS","price_limit":"0.004424778761","sign":true}
bitshares wallet.cpp:3610 bts::wallet::wallet::submit_short
{}
bitshares common_api_client.cpp:5347 bts::rpc_stubs::common_api_client::wallet_market_submit_short
-
suck as usual.crashing all the time
-
It would be nice if the buy/sell order colums listed the quantity of units. (Bitusd etc..)
The depth chart could do with it's own colum, not really usefull now.
Unable to buy/sell 35005 invalid asset ammount
-
Right after the replay, BitShares encountered an exception. I relaunched it and got another:
Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
I had a similar experience. Crashed 3-4 times then made it through the replay to the login screen.
Same here, crashed 2-3 times.
-
will it adds black background then？
-
>Exchange>%market> When I click in the ask or buy orders columns it automatically fills the buy/sell fields which is great, however it often only fills the quantity and not the price, or fills the wrong price.
-
Right after the replay, BitShares encountered an exception. I relaunched it and got another:
Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
I had a similar experience. Crashed 3-4 times then made it through the replay to the login screen.
Same here, crashed 2-3 times.
QT wallet is crashing for me. Here's the console log after it did it's block replay. Re-running the program causes the same exception apart from the initial "successfully replayed / blockchain size changed" lines.
Loading config from file: /home/chris/.BitShares/config.json
Using built-in blockchain checkpoints
Initializing state from built-in genesis file
Successfully replayed 2342769 blocks in 1840 seconds.
Blockchain size changed from 1308MiB to 1310MiB.
/index.html
/css/app.css
/js/app.js
/locale-en.json
/img/xts-logo-xl-white-shadow.png
/img/logo-ico.svg
/img/xt-background.jpg
/webfonts/Roboto-Regular-webfont.woff
/webfonts/fontawesome-webfont.woff
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
/webfonts/Roboto-Regular-webfont.ttf
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
/webfonts/Roboto-Regular-webfont.svg
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
fish: Job 1, “./programs/qt_wallet/bin/BitShares ” terminated by signal SIGSEGV (Address boundary error)
Should be fixed in final release.
-
Getting "invalid asset amount (35005)" when attempting to short bitUSD
getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_short@app.js:46:7953
○ post_short@app.js:43:47902
○ app.js:43:46465
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"430068.550050000020","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"430068.550050000020","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"430068.550050000020"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"430068.550050000020","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"mattjohnson","real_quantity_xts":"430068.550050000020","quote_symbol":"USD","apr":"0.100000000000","collateral_symbol":"BTS","price_limit":"0.004424778761","sign":true}
bitshares wallet.cpp:3610 bts::wallet::wallet::submit_short
{}
bitshares common_api_client.cpp:5347 bts::rpc_stubs::common_api_client::wallet_market_submit_short
Should be fixed in final release.
-
I have 4 GB of ram and I don't have a swap file, but how the heck much ram does this thing need to be happy???
Also I have an update for you. After my last posting I just started it using screen then performed a get_info and the let it run over night.
30 minutes after starting screen...
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 1248189,
"blockchain_head_block_age": "19 weeks old",
"blockchain_head_block_timestamp": "2014-12-12T23:37:50",
"blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6",
"blockchain_average_delegate_participation": "0.01 %",
"blockchain_share_supply": "2,498,315,210.15240 BTS",
"blockchain_blocks_left_in_round": 70,
"blockchain_next_round_time": "at least 12 minutes in the future",
"blockchain_next_round_timestamp": "2015-04-21T19:37:00",
"client_data_dir": "/home/dev/.BitShares",
"client_version": "0.9.0-rc1",
"network_num_connections": 18,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-04-21T19:25:24",
"ntp_time_error": -0.015821000000000002,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "8 days in the future",
"wallet_unlocked_until_timestamp": "2015-04-29T09:30:53",
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Then just a bit ago...
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 1248189,
"blockchain_head_block_age": "19 weeks old",
"blockchain_head_block_timestamp": "2014-12-12T23:37:50",
"blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6",
"blockchain_average_delegate_participation": "0.01 %",
"blockchain_share_supply": "2,498,315,210.15240 BTS",
"blockchain_blocks_left_in_round": 70,
"blockchain_next_round_time": "at least 12 minutes in the future",
"blockchain_next_round_timestamp": "2015-04-22T18:57:50",
"client_data_dir": "/home/dev/.BitShares",
"client_version": "0.9.0-rc1",
"network_num_connections": 14,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-04-22T18:46:11",
"ntp_time_error": 0.188475,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "7 days in the future",
"wallet_unlocked_until_timestamp": "2015-04-29T09:30:53",
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Any particular reason it would be stuck at that block?
Also I'm thinking the memory leak issue might be something else. I let it run all night under screen and the cli is properly responsive still. So maybe not CLI, but maybe something in the syncing process. Since it hasn't synced anything all night???
-
Should be fixed in final release.
Is there going to be another RC rolled before release then? It's not really a good final release candidate if there are known crashes...
While I understand we're still dealing with 0.x releases, starting to formalize the release procedure might be a good idea.
-
Should be fixed in final release.
Is there going to be another RC rolled before release then? It's not really a good final release candidate if there are known crashes...
While I understand we're still dealing with 0.x releases, starting to formalize the release procedure might be a good idea.
I agree with this..
-
Should be fixed in final release.
Is there going to be another RC rolled before release then? It's not really a good final release candidate if there are known crashes...
While I understand we're still dealing with 0.x releases, starting to formalize the release procedure might be a good idea.
I agree with this..
Yea, we will do an RC2 soon and hardfork will be delayed.
-
I don't want to give any more negative burns to muh friends testing, can someone tell me if this has ever been fixed?
https://bitsharestalk.org/index.php/topic,15170.msg197502.html#msg197502 (https://bitsharestalk.org/index.php/topic,15170.msg197502.html#msg197502)
-
I have 4 GB of ram and I don't have a swap file, but how the heck much ram does this thing need to be happy???
Also I have an update for you. After my last posting I just started it using screen then performed a get_info and the let it run over night.
30 minutes after starting screen...
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 1248189,
"blockchain_head_block_age": "19 weeks old",
"blockchain_head_block_timestamp": "2014-12-12T23:37:50",
"blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6",
"blockchain_average_delegate_participation": "0.01 %",
"blockchain_share_supply": "2,498,315,210.15240 BTS",
"blockchain_blocks_left_in_round": 70,
"blockchain_next_round_time": "at least 12 minutes in the future",
"blockchain_next_round_timestamp": "2015-04-21T19:37:00",
"client_data_dir": "/home/dev/.BitShares",
"client_version": "0.9.0-rc1",
"network_num_connections": 18,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-04-21T19:25:24",
"ntp_time_error": -0.015821000000000002,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "8 days in the future",
"wallet_unlocked_until_timestamp": "2015-04-29T09:30:53",
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Then just a bit ago...
default (unlocked) >>> get_info
{
"blockchain_head_block_num": 1248189,
"blockchain_head_block_age": "19 weeks old",
"blockchain_head_block_timestamp": "2014-12-12T23:37:50",
"blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6",
"blockchain_average_delegate_participation": "0.01 %",
"blockchain_share_supply": "2,498,315,210.15240 BTS",
"blockchain_blocks_left_in_round": 70,
"blockchain_next_round_time": "at least 12 minutes in the future",
"blockchain_next_round_timestamp": "2015-04-22T18:57:50",
"client_data_dir": "/home/dev/.BitShares",
"client_version": "0.9.0-rc1",
"network_num_connections": 14,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-04-22T18:46:11",
"ntp_time_error": 0.188475,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "7 days in the future",
"wallet_unlocked_until_timestamp": "2015-04-29T09:30:53",
"wallet_last_scanned_block_timestamp": null,
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Any particular reason it would be stuck at that block?
Also I'm thinking the memory leak issue might be something else. I let it run all night under screen and the cli is properly responsive still. So maybe not CLI, but maybe something in the syncing process. Since it hasn't synced anything all night???
Have you used a chain server??
http://wiki.bitshares.org/index.php/BitShares/Chain-Server
-
RC2: https://bitsharestalk.org/index.php/topic,15900.msg203941.html#msg203941