Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - roadscape

Pages: 1 2 3 4 5 [6] 7 8 9 10 11 12 13 ... 64
76
General Discussion / Re: Cryptofresh Block Explorer + MUSE now available
« on: March 10, 2016, 10:55:44 pm »
Quote from: Akado on March 05, 2016, 11:32:06 am
Quote from: roadscape on March 04, 2016, 10:46:39 pm
Quote from: Akado on March 04, 2016, 09:37:31 pm
Quote from: roadscape on March 04, 2016, 09:32:27 pm
Redesigned page: https://cryptofresh.com/assets -- The motivation for this is to (1) show the most interesting assets first, (2) to be able to check on DEX health at a glance, and (3) to encourage volume competition. I'll add a % change column soon and maybe graphs later on.

Nice, it is really cool now! Could you add the total volume on top? Top right corner of the table for example?

edit: how do you calculate for example OBITS volume? For example, in the OBITS/BTS pair, how do you decide where the volume goes to? BTS or OBITS? Or do some pairs repeat the volume? I mean, BTS trades against all of those pairs.

Done! https://cryptofresh.com/assets

To calculate total OBITS volume, I sum up OBITS volume across all markets it's traded in. To calculate BTS volume, I sum up all BTS that has moved in any of its markets. So perhaps the total 24hr volume needs to be divided by 2? (Since each half of the pair gets full credit.)

Yes I was thinking you would be counting volume twice. Maybe you need to divide it like you said?

Assume I buy 100000 bts with 0.3 BTC, shouldn't the volume be only either 100k bts OR 0.3 btc? Or both? 100k bts AND 0.3 btc were moved so I guess you don't need to divide it? I'm confused now

By cmc standars i guess you should divide it because they mention the market pairs. Obviously in our case it's impossible to show them because they are a lot. http://coinmarketcap.com/exchanges/bitshares-asset-exchange/

I guess I'll leave it as-is unless someone provides a compelling case otherwise. IMO, the way it is now makes the most sense.. and looks better :)

77
Stakeholder Proposals / Re: [Worker Proposal] Blockchain Explorer and API Development
« on: March 10, 2016, 10:51:14 pm »
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC

Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?

I've also been setting up a new development environment so I can perform more testing with witness_node RPC and websocket connections, and just to generally isolate any experiments. In this environment I will also attempt to reproduce the cli_wallet failures that cryptofresh experienced last night to see if I can gleam any more information on the root cause in a less frantic setting.

Aside from backend and maintenance work, the next feature I'd like to add is a 'universal instant search' to quickly locate accounts, assets, and transactions. I'll begin work on that next week.

78
Technical Support / Re: cli_wallet keeps crashing
« on: March 10, 2016, 04:26:39 pm »
Quote from: theoretical on March 10, 2016, 04:14:54 pm
Also the websocketpp deflate code is very new, so it might be a novel bug in websocketpp.  A quick run-through of the websocketpp issue tracker shows some known race condition crash bugs in websocketpp [1] [2] [3] and it is not out of the realm of possibility that one of these leads to a use-after-free.  Some of these bugs are TLS only, so it is possible that disabling TLS fixes the issue.

[1] https://github.com/zaphoyd/websocketpp/issues/459
[2] https://github.com/zaphoyd/websocketpp/issues/451
[3] https://github.com/zaphoyd/websocketpp/issues/336

I am using --rpc-endpoint and not --rpc-tls-endpoint, does this still apply?

If it's helpful I can try to recreate this setup on a separate server today or tomorrow.

79
Technical Support / Re: cli_wallet keeps crashing
« on: March 10, 2016, 04:23:11 pm »
Quote from: theoretical on March 10, 2016, 04:02:07 pm
Possible memory corruption?

If you're running head instead of the last release, there are three changes in FC which might be the cause of the problem:

  • websockets now compress data
  • websocketpp dependency has been updated
  • Use-after-free bug was fixed in future.cpp

If you could run this command:

Code: [Select]
(cd libraries/fc/vendor/websocketpp && git log -1)

it would be useful.  I'm thinking it sounds like you upgraded an existing source checkout, so it might be possible you updated submodules non-recursively, meaning you'd get the new FC code but older websocketpp code, and maybe the new FC code requires more recent websocketpp (I'm just guessing here).

 - I was running head last night, but now I'm on 2.0.160223 (seems to be running much better)
 - My build script always calls git submodule update --init --recursive
 - I'm still using the "existing source checkout" -- I haven't cloned a fresh repo in months
 - Can it be memory corruption even though I restarted both node+wallet many times? (imho it seems more likely the mangled messages are due to compression somehow)

I'm guessing this is not useful now that I've already checked out an older tag, but here's the output:
Code: [Select]
cd libraries/fc/vendor/websocketpp && git log -1
commit c5510d6de04917812b910a8dd44735c1f17061d9
Merge: 13f6da6 f931734
Author: Peter Thorson <git@zaphoyd.com>
Date:   Tue Jun 2 08:55:24 2015 -0400
Could it be a problem with the websocket client I'm using? Perhaps its compression implementation is buggy or something?

80
Technical Support / Re: cli_wallet keeps crashing
« on: March 10, 2016, 03:36:48 pm »
I performed a clean build using 2.0.160223 tag.

Wallet is now running in gdb and I'll keep an eye on it..

81
Technical Support / Re: cli_wallet keeps crashing
« on: March 10, 2016, 02:41:22 pm »
Building @ 36%...

When it's done I'll try running the cli_wallet in gdb and report back with any findings

82
Technical Support / Re: cli_wallet keeps crashing
« on: March 10, 2016, 02:32:37 pm »
xeroc suggested 'try with a plain and empty new wallet by providing the --wallet-file newwallet.json parameter'

I got more stange errors and an unresponsive cli_wallet:

Code: [Select]
    {"str":"{\"methoen_bnotice018params_q[0,[\"0040e76895dbba1c116982218286d077c82062c5\"]]}"}
    th_a  json.cpp:478 from_string
1446545ms th_a       websocket_api.cpp:120         on_message           ] e.to_detail_string(): 4 parse_error_exception: Parse Error
Expected ':' after key "methoen_bnotice018params_q[0,["
    {"key":"methoen_bnotice018params_q[0,["}
    th_a  json.cpp:196 objectFromStream
Error parsing object
    {}
    th_a  json.cpp:218 objectFromStream

    {"str":"{\"methoen_bnotice018params_q[0,[\"0040e769851a9f6ec4457a6a6ea69492772f400b\"]]}"}
    th_a  json.cpp:478 from_string
1449231ms th_a       websocket_api.cpp:120         on_message           ] e.to_detail_string(): 4 parse_error_exception: Parse Error
Expected ':' after key "methoen_bnotice018params_q[0,["
    {"key":"methoen_bnotice018params_q[0,["}
    th_a  json.cpp:196 objectFromStream
Error parsing object
    {}
    th_a  json.cpp:218 objectFromStream

    {"str":"{\"methoen_bnotice018params_q[0,[\"0040e76a38b276e387222c44cf7cc5fd3e213042\"]]}"}
    th_a  json.cpp:478 from_string
1452511ms th_a       websocket_api.cpp:120         on_message           ] e.to_detail_string(): 4 parse_error_exception: Parse Error
Expected ':' after key "methoen_bnotice018params_q[0,["
    {"key":"methoen_bnotice018params_q[0,["}
    th_a  json.cpp:196 objectFromStream
Error parsing object
    {}
    th_a  json.cpp:218 objectFromStream
This looks horribly malformed.. but what would cause this to happen intermittently?

Next I'm trying:
 - make clean and clearing cmake files, rebuilding using tag 2.0.160223
 - connecting to a different ws server (we still can't tell if this is a node or wallet issue)

83
Technical Support / cli_wallet keeps crashing
« on: March 10, 2016, 02:05:45 pm »
Last night I had to update and rebuild the node on the cryptofresh server. The witness_node and cli_wallet had been running smoothly for weeks, but now cli_wallet crashes randomly, on average maybe every 5-15 minutes.

I was getting a different error last night, one that didn't crash cli_wallet, but made it forget how to perform a 'get_object' call. I didn't save that one unfortunately. This morning, I am seeing a more cryptic error:

Code: [Select]
new >>> Server has disconnected us.
9 canceled_exception: Canceled

    {}
    th_a  thread_d.hpp:461 start_next_fiber
1297659ms th_a       wallet.cpp:787                save_wallet_file     ] saving wallet to file wallet.json
1297672ms th_a       http_api.cpp:118              on_request           ] e.to_detail_string(): 9 canceled_exception: Canceled

    {}
    th_a  thread_d.hpp:461 start_next_fiber
1297676ms th_a       http_server.cpp:123           handle_connection    ] unable to read request 9 canceled_exception: Canceled

    {}
    th_a  thread_d.hpp:461 start_next_fiber
pure virtual method called
terminate called without an active exception
./wallet.sh: line 1: 10592 Aborted                 ./programs/cli_wallet/cli_wallet --rpc-http-endpoint="127.0.0.1:8092" -s ws://127.0.0.1:8090
When this happens, I restart the cli_wallet, and everything works fine for another 5-10 minutes.

This is a big PITA for cryptofresh.com.. I'm at my wits end with this issue... any help/leads are appreciated.

I've tried the following to no avail:
 - starting with a new wallet
 - building 'bitshares' latest
 - building 2.0.160302 (failed)
 - building 2.0.160309

84
General Discussion / Re: BitShares now Live on Microsoft Azure Blockchain as a Service (BaaS)
« on: March 10, 2016, 04:52:24 am »
Well done @Fox! +5%

I already received a google alert: https://azure.microsoft.com/es-es/documentation/templates/bitshares-ubuntu-vm/

85
Stakeholder Proposals / Re: [Worker Proposal] Blockchain Explorer and API Development
« on: March 10, 2016, 04:45:37 am »
@Shentist Ok.. fixed! The issue was with the wallet's market history API.. it's supposed to track the latest 200 buckets, but it seems to only track the first 200 buckets. So as a hack a few months ago, I modified my node to track 1000 buckets. And as of a few days ago the BTS-USD market reached 1000 1-hour buckets.. leading to a cutoff of new data.

So now... I track 2000 buckets. 8)

86
Stakeholder Proposals / Re: [Worker Proposal] Blockchain Explorer and API Development
« on: March 10, 2016, 03:05:53 am »
Nevermind, I did see some USD trades go through.. looking into it..

87
Stakeholder Proposals / Re: [Worker Proposal] Blockchain Explorer and API Development
« on: March 10, 2016, 02:54:17 am »
Quote from: Shentist on March 09, 2016, 09:54:51 pm
today the asset page shows for USD "low volume" but this is not correct, maybe something is not right.

This does seem strange.. but as far as I can tell, USD has simply not been traded in the last 24 hours.

88
General Discussion / Re: Cryptofresh Block Explorer + MUSE now available
« on: March 04, 2016, 10:50:20 pm »
Quote from: abit on March 04, 2016, 10:04:45 pm
Quote from: roadscape on March 04, 2016, 09:32:27 pm
Redesigned page: https://cryptofresh.com/assets -- The motivation for this is to (1) show the most interesting assets first, (2) to be able to check on DEX health at a glance, and (3) to encourage volume competition. I'll add a % change column soon and maybe graphs later on.
Good job  +5%

Can you add "daily transfer volume" of each assets to the page? I think it makes much sense.

Thanks @abit! Great idea.. I'm pretty deep in market data for now.. but it does seem like xfer volume may almost be as important as trade volume.

89
General Discussion / Re: Cryptofresh Block Explorer + MUSE now available
« on: March 04, 2016, 10:46:39 pm »
Quote from: Akado on March 04, 2016, 09:37:31 pm
Quote from: roadscape on March 04, 2016, 09:32:27 pm
Redesigned page: https://cryptofresh.com/assets -- The motivation for this is to (1) show the most interesting assets first, (2) to be able to check on DEX health at a glance, and (3) to encourage volume competition. I'll add a % change column soon and maybe graphs later on.

Nice, it is really cool now! Could you add the total volume on top? Top right corner of the table for example?

edit: how do you calculate for example OBITS volume? For example, in the OBITS/BTS pair, how do you decide where the volume goes to? BTS or OBITS? Or do some pairs repeat the volume? I mean, BTS trades against all of those pairs.

Done! https://cryptofresh.com/assets

To calculate total OBITS volume, I sum up OBITS volume across all markets it's traded in. To calculate BTS volume, I sum up all BTS that has moved in any of its markets. So perhaps the total 24hr volume needs to be divided by 2? (Since each half of the pair gets full credit.)

90
General Discussion / Re: Cryptofresh Block Explorer + MUSE now available
« on: March 04, 2016, 09:32:27 pm »
Redesigned page: https://cryptofresh.com/assets -- The motivation for this is to (1) show the most interesting assets first, (2) to be able to check on DEX health at a glance, and (3) to encourage volume competition. I'll add a % change column soon and maybe graphs later on.

Pages: 1 2 3 4 5 [6] 7 8 9 10 11 12 13 ... 64

Page created in 0.025 seconds with 23 queries.