BitShares Forum
Main => General Discussion => Topic started by: vikram on February 07, 2015, 02:59:05 am
-
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.6.0
Please only use this thread to post constructive feedback that may be useful to the development team.
-
I've installed the client on a brand new machine and running through some tests.
1. Failing registering username faucet through Google
It let me enter my credentials the first time and failed. Every time I go back to it I get the message below.
"We're sorry, but something went wrong.
If you are the application owner check the logs for more information "
Where do I find these logs?
-
Serious problem
On Korean windows, all menus are broken - cannot distinguish anything
Please resolve this problem ASAP
PS. I tried other languages on Korean Windows, but they all fail (showing "ko" only)
(http://i.imgur.com/OxerRRc.png)
-
I have downloaded and synced 0.6.0
My problem of not being able to cancel a bitSILVER order, which was supposed to be corrected with this release, still exists.
I am getting the message "insufficient relay fee (36005)"
PROBLEM HAS BEEN SOLVED BY TEMPORARILY CHANGING TRANSACTION FEE FROM 0.1 to 0.5
https://bitsharestalk.org/index.php?topic=13812.msg179677#msg179677
Also, I can't see how to navigate to Console in this new release.
-
I have downloaded and synced 0.6.0
My problem of not being able to cancel a bitSILVER order, which was supposed to be corrected with this release, still exists.
https://bitsharestalk.org/index.php?topic=13812.msg179677#msg179677
Also, I can't see how to navigate to Console in this new release.
Yep, it's harder to find the console now; personally I preferred when it was easier to access. Press the "Advanced" button, then click on the console tab.
-
Advanced
When I click the advanced button, there's no real indicator to let the user know they are in an advanced mode. I see preferences and console, it would be nice for some advanced mode indicator. When I went back to the advanced mode menu, I expected a toggle to go back to a standard mode.
Wallet Ran First Time
I'd like to see something warning the user that downloading the entire blockchain will take some time. Put the user at ease that this is perfectly normal.
-
I have downloaded and synced 0.6.0
My problem of not being able to cancel a bitSILVER order, which was supposed to be corrected with this release, still exists.
I am getting the message "insufficient relay fee (36005)"
PROBLEM HAS BEEN SOLVED BY TEMPORARILY CHANGING TRANSACTION FEE FROM 0.1 to 0.5
https://bitsharestalk.org/index.php?topic=13812.msg179677#msg179677
Also, I can't see how to navigate to Console in this new release.
The fix will not take effect until after the hardfork.
-
Margin Call Orders are missing
+ Short order columns are too wide...
-
I've installed the client on a brand new machine and running through some tests.
1. Failing registering username faucet through Google
It let me enter my credentials the first time and failed. Every time I go back to it I get the message below.
"We're sorry, but something went wrong.
If you are the application owner check the logs for more information "
Where do I find these logs?
Extremely frustrating. I tried creating another account, restarting the client, clearly browser cache, still same error with the faucet through Google, Twitter and client options.
-
Win GUI.
Details on errors do not display.
The bell icon shows the error, but clicking on show details doesn't do a thing
When removing a market, from the recent market section, it removes the market. But you get forwarded to another market
Like clayop said margin call orders are missing, but it also seems that price limits and total bitasset (per short) are not being displayed. Sorry it is displayed, apparently you can sidescroll the short sell orders tab, wich isn't quit obvious.
To look at a particular asset, and see the collected fees, price feeds etc... You now have to go to exchange and click on it. But there is no way in the GUI to see this page for BTS itself.
-
I have downloaded and synced 0.6.0
My problem of not being able to cancel a bitSILVER order, which was supposed to be corrected with this release, still exists.
https://bitsharestalk.org/index.php?topic=13812.msg179677#msg179677
Also, I can't see how to navigate to Console in this new release.
Yep, it's harder to find the console now; personally I preferred when it was easier to access. Press the "Advanced" button, then click on the console tab.
+5%
-
I have downloaded and synced 0.6.0
My problem of not being able to cancel a bitSILVER order, which was supposed to be corrected with this release, still exists.
https://bitsharestalk.org/index.php?topic=13812.msg179677#msg179677
Also, I can't see how to navigate to Console in this new release.
Yep, it's harder to find the console now; personally I preferred when it was easier to access. Press the "Advanced" button, then click on the console tab.
+5%
What about separating console button from advanced menu, and locating advanced button next to notification button?
-
I've fixed the following so far this morning:
- Recent market remove button
- Transaction fee minimum now set to 0.1
- Cover orders (I also added some proper sorting and saturation of shorts at the feed price
- Also added translation fields for the update preferences warnings
Not sure why Korean doesn't work, it works fine using the browser.
The faucet problem seems to be on the faucet end, I'm sure valzav will look into it later.
-
.BUG~buG
first time start client,it can sync,but after it ,clients cannot sync while client is ruining
(http://ww1.sinaimg.cn/large/005X3q9sjw1ep11s8l5jej30bu03xglj.jpg)
-
I've installed the client on a brand new machine and running through some tests.
1. Failing registering username faucet through Google
It let me enter my credentials the first time and failed. Every time I go back to it I get the message below.
"We're sorry, but something went wrong.
If you are the application owner check the logs for more information "
Where do I find these logs?
I've fixed the faucet, could you try to register it again?
-
on "Exchange" I don't see anymore anything to have access to any market !!! (except 2 Recent Market's on the upper right)
(http://3.bp.blogspot.com/-zOjLelmbpW8/VNY6oVsD-KI/AAAAAAAADVI/ASxl4CnUD8Q/s1600/market.png)
-
problems collected from the chinese community:
1. in transaction tab, the GUI can only show 9 assets max, but actually I have 10:
(http://i.imgur.com/p6Ph8IT.png)
2. No response when clicking [show details] on the upper right:
(http://i.imgur.com/zzXa2xR.png)
3. No chinese localization of menu bar of qt wallet:
(http://i.imgur.com/2BX4B4N.jpg)
4. the ram consumption is even higher than 0.5.3 (up to 1.5gb):
(http://i.imgur.com/HO31dVF.png)
5. the color of the following texts should be darker to be seen with comfort:
(http://i.imgur.com/XKZFBvE.png)
6. the margin call orders are all empty?
(http://i.imgur.com/vohYF1F.jpg)
7. while unlocking the GUI wallet, sometimes the GUI would never unlock and only shows endlessly three circulating dots.
8. incomplete chinese localization of some places:
(http://i.imgur.com/3EkpRqE.jpg)
(http://i.imgur.com/jKXK9Uf.jpg)
(http://i.imgur.com/0vaq7s0.jpg)
-
Allow including non-delegate IDs in voting slates for off-chain polling
Do you have safe-gaurds set up so that once a non-delegate account as a ton of votes, it can't register as a delegate and start signing blocks?
Also, what makes this 'off-chain'? Isn't this 'on-chain'?
-
on "Exchange" I don't see anymore anything to have access to any market !!! (except 2 Recent Market's on the upper right)
(http://3.bp.blogspot.com/-zOjLelmbpW8/VNY6oVsD-KI/AAAAAAAADVI/ASxl4CnUD8Q/s1600/market.png)
after I rebuild index it was solved ...
I can see the markets now!!!!
-
Allow including non-delegate IDs in voting slates for off-chain polling
Do you have safe-gaurds set up so that once a non-delegate account as a ton of votes, it can't register as a delegate and start signing blocks?
Also, what makes this 'off-chain'? Isn't this 'on-chain'?
Okay I've changed the line to read: "Allow including negative IDs in voting slates for shareholder polling"
-
1729862 2015-02-07T19:24:20 anchor.crazybit 0 166 0 0 0000000000000000000000000000000000000000
1729861 2015-02-07T19:24:10 coolspeed 0 166 0 0 0000000000000000000000000000000000000000
1729860 2015-02-07T19:24:00 kokojie 0 166 0 0 0000000000000000000000000000000000000000
1729859 2015-02-07T19:23:50 delegate.btsnow 0 166 0 0 0000000000000000000000000000000000000000
1729858 2015-02-07T19:23:40 emski 0 166 0 0 0000000000000000000000000000000000000000
1729857 2015-02-07T19:23:30 delegate.taolje 0 166 0 0 0000000000000000000000000000000000000000
1729856 2015-02-07T19:23:20 delegate1.john-galt 0 166 0 0 0000000000000000000000000000000000000000
1729855 2015-02-07T19:23:10 spartako2 2 1332 0 0 0000000000000000000000000000000000000000
1729854 2015-02-07T19:23:00 init0 0 166 0 0 0000000000000000000000000000000000000000
1729853 2015-02-07T19:22:50 delegate.webber 0 166 0 0 0000000000000000000000000000000000000000
1729852 2015-02-07T19:22:40 market.cn.group101 0 166 0 0 0000000000000000000000000000000000000000
1729851 2015-02-07T19:22:30 delegate.cgafeng 0 166 0 0 0000000000000000000000000000000000000000
1729850 2015-02-07T19:22:20 www.minebitshares-com 0 166 0 0 0000000000000000000000000000000000000000
1729849 2015-02-07T19:22:10 delegate.charity 0 166 0 0 0000000000000000000000000000000000000000
1729848 2015-02-07T19:22:00 calabiyau 0 166 0 0 0000000000000000000000000000000000000000
1729847 2015-02-07T19:21:50 dev0.theoretical 0 166 0 0 0000000000000000000000000000000000000000
1729846 2015-02-07T19:21:40 elmato 0 166 0 0 0000000000000000000000000000000000000000
1729845 2015-02-07T19:21:30 delegate-dev4.btsnow 0 166 0 0 0000000000000000000000000000000000000000
1729844 2015-02-07T19:21:20 go.heaven 1 1826 0 0 0000000000000000000000000000000000000000
1729843 2015-02-07T19:21:10 dev0.nikolai 1 1910 0 0 0000000000000000000000000000000000000000
no randomness?
-
1729862 2015-02-07T19:24:20 anchor.crazybit 0 166 0 0 0000000000000000000000000000000000000000
1729861 2015-02-07T19:24:10 coolspeed 0 166 0 0 0000000000000000000000000000000000000000
1729860 2015-02-07T19:24:00 kokojie 0 166 0 0 0000000000000000000000000000000000000000
1729859 2015-02-07T19:23:50 delegate.btsnow 0 166 0 0 0000000000000000000000000000000000000000
1729858 2015-02-07T19:23:40 emski 0 166 0 0 0000000000000000000000000000000000000000
1729857 2015-02-07T19:23:30 delegate.taolje 0 166 0 0 0000000000000000000000000000000000000000
1729856 2015-02-07T19:23:20 delegate1.john-galt 0 166 0 0 0000000000000000000000000000000000000000
1729855 2015-02-07T19:23:10 spartako2 2 1332 0 0 0000000000000000000000000000000000000000
1729854 2015-02-07T19:23:00 init0 0 166 0 0 0000000000000000000000000000000000000000
1729853 2015-02-07T19:22:50 delegate.webber 0 166 0 0 0000000000000000000000000000000000000000
1729852 2015-02-07T19:22:40 market.cn.group101 0 166 0 0 0000000000000000000000000000000000000000
1729851 2015-02-07T19:22:30 delegate.cgafeng 0 166 0 0 0000000000000000000000000000000000000000
1729850 2015-02-07T19:22:20 www.minebitshares-com 0 166 0 0 0000000000000000000000000000000000000000
1729849 2015-02-07T19:22:10 delegate.charity 0 166 0 0 0000000000000000000000000000000000000000
1729848 2015-02-07T19:22:00 calabiyau 0 166 0 0 0000000000000000000000000000000000000000
1729847 2015-02-07T19:21:50 dev0.theoretical 0 166 0 0 0000000000000000000000000000000000000000
1729846 2015-02-07T19:21:40 elmato 0 166 0 0 0000000000000000000000000000000000000000
1729845 2015-02-07T19:21:30 delegate-dev4.btsnow 0 166 0 0 0000000000000000000000000000000000000000
1729844 2015-02-07T19:21:20 go.heaven 1 1826 0 0 0000000000000000000000000000000000000000
1729843 2015-02-07T19:21:10 dev0.nikolai 1 1910 0 0 0000000000000000000000000000000000000000
no randomness?
You need to re-index with --statistics-enabled flag now to track extra info (such as current random seed) in the block records.
-
Oh .. i see .. i guess I dont need that for a delegate?
-
Oh .. i see .. i guess I dont need that for a delegate?
Correct, we only disabled some optional information tracking. Delegates and normal users still operate normally. The additional info is pretty much only useful to block explorers, people doing tech support, or the curious.
-
Oh .. i see .. i guess I dont need that for a delegate?
Correct, we only disabled some optional information tracking. Delegates and normal users still operate normally. The additional info is pretty much only useful to block explorers, people doing tech support, or the curious.
I conclude:
- this feature results in less disk usage
- some of us (me included) should have at least one machine runnimg with all stats active
Are there more parameters i should enable to have the full thing in the databases?
-
Oh .. i see .. i guess I dont need that for a delegate?
Correct, we only disabled some optional information tracking. Delegates and normal users still operate normally. The additional info is pretty much only useful to block explorers, people doing tech support, or the curious.
I conclude:
- this feature results in less disk usage
- some of us (me included) should have at least one machine runnimg with all stats active
Are there more parameters i should enable to have the full thing in the databases?
Less disk usage and less disk accesses and processing while syncing/reindexing. You just need --statistics-enabled and have to reindex, or set it to true in your config.json so you don't have to give the extra flag for every future reindex too.
I'll probably enable it on my delegate since its a node that's always running and it's handy to use when querying info for tech support occasionally.
Also it needs to be enabled for light wallet servers.
-
It's getting harder and harder to sync or replay the blockhain with a PC that has HDD. And i'm not even using GUI now. In a few months it will not be just hard but rather impossible. And it's not like it uses the whole RAM or CPU, but just overloads the HDD. Is it because of 10 sec block target ? Seems like this is a major problem :-X
-
.BUG~buG
first time start client,it can sync,but after it ,clients cannot sync while client is ruining
(http://ww1.sinaimg.cn/large/005X3q9sjw1ep11s8l5jej30bu03xglj.jpg)
I'm having the same issue, I have 18 network connections. I've restarted twice and let it run 15 minutes at a time (11h 39m).
-
It's getting harder and harder to sync or replay the blockhain with a PC that has HDD. And i'm not even using GUI now. In a few months it will not be just hard but rather impossible. And it's not like it uses the whole RAM or CPU, but just overloads the HDD. Is it because of 10 sec block target ? Seems like this is a major problem :-X
.BUG~buG
first time start client,it can sync,but after it ,clients cannot sync while client is ruining
(http://ww1.sinaimg.cn/large/005X3q9sjw1ep11s8l5jej30bu03xglj.jpg)
I'm having the same issue, I have 18 network connections. I've restarted twice and let it run 15 minutes at a time (11h 39m).
Try running the Windows bitshares console under \Program Files\BitSharesX\bin\bitshares_client.exe its syncing the blocks consistently compare to GUI, once synced then you can open the GUI.
and use Memory Improve Master software to manage the memory problem.
-
I have tried both building 0.5.3 myself and using the pre-compiled 0.5.1 binaries. The results are the same: the clients are totally unusable.
The CLI client of both versions still has the unbearable typing lag I mentioned last time. Running it with --server and using the web wallet doesn't help. It is very slow. The RPC POST requests have an average latency of around 2 minutes and some of them timeout with an error!
The Qt client isn't better. The 0.5.3 Qt client is very slow and laggy and sometimes won't ever load pages like the market. In fact it completely froze my Ubuntu system (hard reset required) when I tried to load the market in an attempt to cover a short! The performance of the 0.5.1 Qt client was actually pretty decent, but I quickly realized the only reason that was the case was because the blockchain wasn't syncing at all beyond the point left by the CLI client (a problem I mentioned last time with v0.4.27.2), meaning its completely worthless.
So basically there is no properly functioning client for me at the moment. I only have 4 GB of RAM on the laptop so I didn't expect super snappy performance with the full client, but this is just ridiculous. It has to be some bug in the client right? Or is my computer somehow messed up?
Please let me know if these performance problems are still present in 0.6.0.
The blockchain replay on initial start of v0.6.0 of bitshares_client took a pretty long time (specifically, it took 12931 seconds to replay 1643284 blocks, or an average rate of 127 blocks/second) but at least it wasn't too taxing on my computer which allowed me to comfortably multitask. But this was only up to the block as of 10 days ago (last time I synced the BitShares blockchain).
So then I let the client sync the remaining 10 days of blocks. During this time it was taxing my computer noticeably more than during replay but it was still okay for multitasking [1]. However, bitshares_client was experiencing the horrible typing lag (this is with the wallet closed). The remaining syncing took approximately 110 minutes, so that was another 1735192-1643284=91908 blocks in roughly 6600 seconds, which is an average of 14 blocks/second. That average rate is significantly smaller than the 127 blocks/second replay rate, but to be fair the replay rate was an average over many blocks and I did notice that the instantaneous replay rate significantly slowed over time (meaning the syncing rate seems to get worse as the blockchain/database evolves over time). The typical IO usage during this syncing process was roughly 7 MB/s disk read and roughly 200 KB/s disk write (although towards the last few days worth of blocks that it was syncing the write rate had dropped to somewhere around 75 KB/s).
Actually, what was interesting is that the client never really synced. It reached close to the head block but was always 10 to 20 seconds behind. The typing lag remained. The virtual memory usage was above 5.5 GB and the resident memory usage was about 2 GB. And it was still heavily taxing my computer. So, I closed bitshares_client and then restarted.
When bitshares_client started up again, it exhibited no typing lag and I was able to see that it was 4 minutes behind. Within a few seconds, it synced to the present head block (< 10 seconds behind). It again still exhibited no typing lag. It was able to keep the blockchain in sync while barely taxing the computer. During this time the disk read usage was typically around 5 MB/s and the disk write usage was typically under 10 KB/s. The initial memory usage was a little over 2 GB in virtual memory, a little over 600 MB in resident memory, and a little over 200 MB in shared memory. This is all with the wallet still closed.
Then, I unlocked the wallet. The wallet scanning finished quickly. Everything was still running smoothly. No typing lag, no trouble maintaining sync. The previous problem I had reported (https://bitsharestalk.org/index.php?topic=13647.msg178553#msg178553) seems to be solved (thanks Vikram! (https://github.com/BitShares/bitshares/commit/1d67a9bca519b8e417f3d2507324a98a7e2e3a1d)).
So, what I have learned from this is that there was a performance bug with the client when the wallet is unlocked that existed in 0.5.3 and was solved with 0.6.0, that the client still has a lot of trouble initially syncing the blockchain to the present after being offline for a while (at least on my computer with 4 GB of RAM and a HDD), and that the blockchain syncing gets significantly worse over time and the client uses more and more memory (seemingly unnecessarily) which is why it probably makes sense to restart the client after some amount of syncing in those cases so that it can start fresh. It also suggests to sync the blockchain more frequently (I guess I need to make it a habit to sync the blockchain once a day even when I have no use for it).
[1] This is not entirely true. First, I noticed that the memory usage of bitshares_client steadily increased over time (resident memory had grown over 2 GB near the end of the sync; virtual memory was over 5.5 GB). At some point during the syncing process, Chrome (which I was using at the time) started using the disk a lot too (maybe because RAM became even more scarce than normal?) and that combined with the IO usage of bitshares_client seems to have really brought my computer to its knees. I wasn't able to investigate carefully because I was just trying to fix the problem before I would be forced into hard resetting the computer. There was a period of time (several minutes) where the entire computer GUI was frozen so badly and it took me minutes to just switch to a console to type the command "killall chrome" and regain usable control of my computer. The conclusion I am reaching is that I cannot actually both run Chrome and sync the blockchain to the present after a long time of being offline using bitshares_client at the same time on my computer. : (
-
It's the third time now it re-syncs the whole blockchain from the beginning without asking me to reset the database or continue normally as he did in past...
And for not obvious reason! I didn't make any transaction, just closed and reopened the client... Must wait again >:(
-
I've installed the client on a brand new machine and running through some tests.
1. Failing registering username faucet through Google
It let me enter my credentials the first time and failed. Every time I go back to it I get the message below.
"We're sorry, but something went wrong.
If you are the application owner check the logs for more information "
Where do I find these logs?
I've fixed the faucet, could you try to register it again?
Fixed.
-
(http://i62.tinypic.com/9hnjo1.jpg)
I don't see an option to submit my choice to receive the news letter. If I just need to select the radio button for submission, it would be great to have some type of feedback from the system. 'Thank you for..'
-
It's the third time now it re-syncs the whole blockchain from the beginning without asking me to reset the database or continue normally as he did in past...
And for not obvious reason! I didn't make any transaction, just closed and reopened the client... Must wait again >:(
This happens to me, but only if i launch 2 instances of BitShares.exe.
-
Cosmetic recommendation
"Warning! Scammers often make fake accounts to trick people into sending their funds to the wrong place. Please triple-check the name you have entered."
Could we possibly have a Precautions - Read Before Sending link instead? When the user clicks on it, the original text then appears below it. The keywords that stick out to me when I'm first exploring the wallet is scammer and fake accounts.
-
Cosmetic recommendation
"Warning! Scammers often make fake accounts to trick people into sending their funds to the wrong place. Please triple-check the name you have entered."
Could we possibly have a Precautions - Read Before Sending link instead? When the user clicks on it, the original text then appears below it. The keywords that stick out to me when I'm first exploring the wallet is scammer and fake accounts.
you know how to do pull request?
https://github.com/BitShares/web_wallet/blob/master/app/static/locale-en.json
If not just send me the modified version and I can send a pull request for you
-
Cosmetic recommendation
"Warning! Scammers often make fake accounts to trick people into sending their funds to the wrong place. Please triple-check the name you have entered."
Could we possibly have a Precautions - Read Before Sending link instead? When the user clicks on it, the original text then appears below it. The keywords that stick out to me when I'm first exploring the wallet is scammer and fake accounts.
you know how to do pull request?
https://github.com/BitShares/web_wallet/blob/master/app/static/locale-en.json
If not just send me the modified version and I can send a pull request for you
Thank you for the response. I will find a quick YouTube pull request vid. :)
-
The wallet is faster and much more stable.
I can leave the market open for extended periods of time and it doesn't melt my CPU +5%
-
Serious problem
On Korean windows, all menus are broken - cannot distinguish anything
Please resolve this problem ASAP
PS. I tried other languages on Korean Windows, but they all fail (showing "ko" only)
【Major GUI Issue】
1. Had the same issue on Mac.
A specific language translation file does not fix the problem. Forcing user to use the system language is not acceptible even if you had the completed translation, if I give feedback at the standard level of a mature GUI product. Leaving the system language as the default language and allowing the user to change it later is acceptible, if you have a completed translation.
【Minor GUI Issue】
2. When I press command + comma, it returned nothing.
Sorry but I don't quite know how to submit a github issue, or whether it is expected.
-
If I leave the UIA (CFSGold) for couple of minutes the wallet crash. It happened every time.
-
There's a short on the GOLD/BTS market with insufficient collateral to cover 1 GOLDtoshi. This has undesirable consequences: https://github.com/BitShares/bitshares/issues/923#issuecomment-73495730
-
{u'id': 0, u'error': {u'message': u'Assert Exception (10)\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n\n', u'code': 10, u'detail': u'10
+assert_exception: Assert Exception\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n {"method_name":"ask"}\n th_a general_api.cpp:187 batch\n\n {}\n th_a
+common_api_client.cpp:240 batch'}}
Can't run 'ask' through RPC. Via client it works fine .. not via RPC .. what has changed?
-
Fantastic color change from bright blue to dark grey blue. This keeps my Cylon eye from straining.
Much more professional looking. Whoever had that idea is winning.
-
I am not able to find "console" in this version. where is it hiding ?
-
I am not able to find "console" in this version. where is it hiding ?
On the right click on username->advanced->second tab is console
-
There is a serious mistake:6.0 block random_seed is all zero.
-
There is a serious mistake:6.0 block random_seed is all zero.
No mistake. Please see: https://bitsharestalk.org/index.php?topic=14083.msg183402#msg183402
-
after a bitEURO buy order the gui closed on my linux system and when I restarted even I answered to continue normally, a critical error occurred and it synced again from the beginning! not to mention it takes to long to fully sync... I don't want to imagine how long it will take after a year to download the whole blockchain...
Sent from my ALCATEL ONE TOUCH 997D
-
I notice it uses over 2 gigs ram when downloading the chain.. my VPS has 2 gigs total and throws up (out of memory exception).. its been a whole day wasted getting it to work.. i created a 4 gig swap file just so it can sync up.
After a while it slows down to a crawl and I have to start it up again so it will sync faster.
-
{u'id': 0, u'error': {u'message': u'Assert Exception (10)\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n\n', u'code': 10, u'detail': u'10
+assert_exception: Assert Exception\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n {"method_name":"ask"}\n th_a general_api.cpp:187 batch\n\n {}\n th_a
+common_api_client.cpp:240 batch'}}
Can't run 'ask' through RPC. Via client it works fine .. not via RPC .. what has changed?
@vikram : can you help me out here?
-
{u'id': 0, u'error': {u'message': u'Assert Exception (10)\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n\n', u'code': 10, u'detail': u'10
+assert_exception: Assert Exception\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n {"method_name":"ask"}\n th_a general_api.cpp:187 batch\n\n {}\n th_a
+common_api_client.cpp:240 batch'}}
Can't run 'ask' through RPC. Via client it works fine .. not via RPC .. what has changed?
@vikram : can you help me out here?
I believe this was a security issue that was fixed: https://github.com/BitShares/bitshares/commit/7dd7d6154d46abfd79a1cb26bdcf0eeecf0dd4c3
If you want to automate market orders, you can use wallet_market_batch_update.
-
{u'id': 0, u'error': {u'message': u'Assert Exception (10)\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n\n', u'code': 10, u'detail': u'10
+assert_exception: Assert Exception\n_self->get_rpc_server()->get_method_data(method_name).prerequisites == bts::api::no_prerequisites: ask\n {"method_name":"ask"}\n th_a general_api.cpp:187 batch\n\n {}\n th_a
+common_api_client.cpp:240 batch'}}
Can't run 'ask' through RPC. Via client it works fine .. not via RPC .. what has changed?
@vikram : can you help me out here?
I believe this was a security issue that was fixed: https://github.com/BitShares/bitshares/commit/7dd7d6154d46abfd79a1cb26bdcf0eeecf0dd4c3
If you want to automate market orders, you can use wallet_market_batch_update.
ah .. thought so .. thanks for clarification
-
Hm .. this kind of results in some serious headache considering that I cannot run any command from outside the client even if my clients are secured by a VPN network ..
What do I have to do be allowed to run json_authenticated commands via RPC? Can you help me authenticate to the client via python?
What commands require an encrypted json authentication?
-
Hm .. this kind of results in some serious headache considering that I cannot run any command from outside the client even if my clients are secured by a VPN network ..
What do I have to do be allowed to run json_authenticated commands via RPC? Can you help me authenticate to the client via python?
What commands require an encrypted json authentication?
If you message modprobe, I think he should be able to help.