Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Cryptofresh Block Explorer + MUSE now available  (Read 10442 times)

0 Members and 1 Guest are viewing this topic.


Offline abit

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #106 on: January 01, 2016, 04:34:52 PM »
"yun-bts" is on the top of "Inactive Proxies" but it's an exchange account.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline Riverhead

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #107 on: January 01, 2016, 06:24:07 PM »


Thanks riverhead :) I need to improve the caching layer.. but witness votes are fixed for now. Do you still see the rounding issue?

Rounding still an issue. Just need to look at a Muse balance in both the client and on Crypyofresh. For most purposes the rounding isn't a problem - I can still see transfers and don't need to see them in fine precision.


Offline abit

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #108 on: January 02, 2016, 05:54:26 PM »
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12065
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: Cryptofresh Block Explorer + MUSE now available
« Reply #109 on: January 02, 2016, 06:25:27 PM »
Once a proposal has been approved or expired, the proposal's is removed and not shown by the API.
Not sure what the reason for this is ..
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline roadscape

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #110 on: January 05, 2016, 12:43:14 AM »
"yun-bts" is on the top of "Inactive Proxies" but it's an exchange account.

Fixed!

Rounding still an issue. Just need to look at a Muse balance in both the client and on Crypyofresh. For most purposes the rounding isn't a problem - I can still see transfers and don't need to see them in fine precision.

Aaah. That rounding. Yes.. I agree this is an issue. IMO the ideal fix would be to have a rounding on/off toggle. I do think rounding makes it much easier on the eyes but users need to have the ability to see the raw values.

http://cryptofresh.com/p/1.10.46 page not found.

As @xeroc said, proposals disappear from the API after they've been approved or expired. I did implement 'permanent' caching for committee proposals... I'll go ahead and make it more aggressive, as this one appears to have fallen through the cracks.
http://cryptofresh.com  |  witness: roadscape

Offline kenCode

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #111 on: January 05, 2016, 08:10:32 AM »
Rounding still an issue. Just need to look at a Muse balance in both the client and on Crypyofresh. For most purposes the rounding isn't a problem - I can still see transfers and don't need to see them in fine precision.
Aaah. That rounding. Yes.. I agree this is an issue. IMO the ideal fix would be to have a rounding on/off toggle. I do think rounding makes it much easier on the eyes but users need to have the ability to see the raw values.

 
I haven't followed this rounding issue, but it sounds like if the number is really long and screws up the display and makes it tough on the eyes, you could just truncate all numbers to just a few digits after the decimal and use a tooltip to display the rest of it with a dotted text-decoration to indicate there is more digits available with that number. The ideal tooltip actually stays put onClick so that you can give users the option to select the full number too for copy/paste procedures etc. Sorry if I'm way off base here, just trying to help.


Offline btswolf

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #113 on: January 05, 2016, 08:51:35 PM »
Site is down:
 
We're sorry, but something went wrong.
------------------------------------------------
If you are the application owner check the logs for more information.

I like cryptofresh but it would be even greater to have that stats directly integrated to OL.

Offline roadscape

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #114 on: January 05, 2016, 08:56:45 PM »
Site is down:
 
We're sorry, but something went wrong.
------------------------------------------------
If you are the application owner check the logs for more information.

Thanks Ken.. looking into it. witness_node was frozen, and I'm having trouble getting it running again..

Code: [Select]
3229214ms th_a       witness.cpp:86                plugin_initialize    ] witness plugin:  plugin_initialize() begin
3229214ms th_a       witness.cpp:96                plugin_initialize    ] key_id_to_wif_pair: ["......","....."]
3229214ms th_a       witness.cpp:114               plugin_initialize    ] witness plugin:  plugin_initialize() end
3229214ms th_a       application.cpp:354           startup              ] Replaying blockchain on user request.
3229214ms th_a       application.cpp:292           operator()           ] Initializing database...
3243588ms th_a       db_management.cpp:48          reindex              ] reindexing blockchain
3243590ms th_a       db_management.cpp:101         wipe                 ] Wiping database
3243620ms th_a       object_database.cpp:84        wipe                 ] Wiping object database...
3243643ms th_a       object_database.cpp:86        wipe                 ] Done wiping object databse.
3243643ms th_a       object_database.cpp:91        open                 ] Opening object database from /home/bitshares-2/witness_node_data_dir/blockchain ...
3243643ms th_a       object_database.cpp:97        open                 ] Done opening object database.
3257917ms th_a       db_debug.cpp:82               debug_dump           ] total_balances[asset_id_type()].value: 12205723874026 core_asset_data.current_supply.value: 253409943611989
3257951ms th_a       db_management.cpp:55          reindex              ] !no last block
3257951ms th_a       db_management.cpp:56          reindex              ] last_block:
3258068ms th_a       thread.cpp:95                 thread               ] name:ntp tid:140271469905664
3258080ms th_a       thread.cpp:95                 thread               ] name:p2p tid:140271448925952
3258091ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 83.221.132.47:1776
3258130ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 7706 us
3258170ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 188.40.91.213:1776
[....]
3258535ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 109.73.172.144:50696
3258536ms th_a       application.cpp:184           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:56537
3258542ms th_a       application.cpp:234           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
3258543ms th_a       witness.cpp:119               plugin_startup       ] witness plugin:  plugin_startup() begin
3258543ms th_a       witness.cpp:136               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
3258543ms th_a       witness.cpp:137               plugin_startup       ] witness plugin:  plugin_startup() end
3258543ms th_a       main.cpp:176                  main                 ] Started witness node on a chain with 0 blocks.
3258543ms th_a       main.cpp:177                  main                 ] Chain ID is 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8
[end of output]

Haven't seen this before,, any ideas?
http://cryptofresh.com  |  witness: roadscape

Offline abit

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #115 on: January 05, 2016, 11:38:15 PM »
Site is down:
 
We're sorry, but something went wrong.
------------------------------------------------
If you are the application owner check the logs for more information.

Thanks Ken.. looking into it. witness_node was frozen, and I'm having trouble getting it running again..

Code: [Select]
3229214ms th_a       witness.cpp:86                plugin_initialize    ] witness plugin:  plugin_initialize() begin
3229214ms th_a       witness.cpp:96                plugin_initialize    ] key_id_to_wif_pair: ["......","....."]
3229214ms th_a       witness.cpp:114               plugin_initialize    ] witness plugin:  plugin_initialize() end
3229214ms th_a       application.cpp:354           startup              ] Replaying blockchain on user request.
3229214ms th_a       application.cpp:292           operator()           ] Initializing database...
3243588ms th_a       db_management.cpp:48          reindex              ] reindexing blockchain
3243590ms th_a       db_management.cpp:101         wipe                 ] Wiping database
3243620ms th_a       object_database.cpp:84        wipe                 ] Wiping object database...
3243643ms th_a       object_database.cpp:86        wipe                 ] Done wiping object databse.
3243643ms th_a       object_database.cpp:91        open                 ] Opening object database from /home/bitshares-2/witness_node_data_dir/blockchain ...
3243643ms th_a       object_database.cpp:97        open                 ] Done opening object database.
3257917ms th_a       db_debug.cpp:82               debug_dump           ] total_balances[asset_id_type()].value: 12205723874026 core_asset_data.current_supply.value: 253409943611989
3257951ms th_a       db_management.cpp:55          reindex              ] !no last block
3257951ms th_a       db_management.cpp:56          reindex              ] last_block:
3258068ms th_a       thread.cpp:95                 thread               ] name:ntp tid:140271469905664
3258080ms th_a       thread.cpp:95                 thread               ] name:p2p tid:140271448925952
3258091ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 83.221.132.47:1776
3258130ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 7706 us
3258170ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 188.40.91.213:1776
[....]
3258535ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 109.73.172.144:50696
3258536ms th_a       application.cpp:184           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:56537
3258542ms th_a       application.cpp:234           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
3258543ms th_a       witness.cpp:119               plugin_startup       ] witness plugin:  plugin_startup() begin
3258543ms th_a       witness.cpp:136               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
3258543ms th_a       witness.cpp:137               plugin_startup       ] witness plugin:  plugin_startup() end
3258543ms th_a       main.cpp:176                  main                 ] Started witness node on a chain with 0 blocks.
3258543ms th_a       main.cpp:177                  main                 ] Chain ID is 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8
[end of output]

Haven't seen this before,, any ideas?
Sometimes when I had this "can't start" issue is because another witness_node process is running and listening on the same port.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline abit

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #116 on: January 07, 2016, 08:45:16 AM »
'We're sorry, but something went wrong."  :-[
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline cass

  • Hero Member
  • *****
  • Posts: 4324
  • /(┬.┬)\
    • View Profile
Re: Cryptofresh Block Explorer + MUSE now available
« Reply #117 on: January 07, 2016, 10:33:57 AM »
same here …
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline roadscape

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #118 on: January 07, 2016, 01:58:57 PM »
Sorry for the downtime guys, witness_node froze again.. bringing it back up..

Code: [Select]
798084ms th_a       application.cpp:497           handle_block         ] Got block: #2447427 time: 2016-01-07T08:13:18 latency: 85 ms from: maqifrnswa  irreversible: 2447408 (-19)
798264ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
799293ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
800307ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
800407ms th_a       application.cpp:546           handle_transaction   ] Got 1 transactions from network
801321ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
801345ms th_a       application.cpp:497           handle_block         ] Got block: #2447428 time: 2016-01-07T08:13:21 latency: 346 ms from: bitcube  irreversible: 2447408 (-20)
[stuck]
^C
Program received signal SIGINT, Interrupt.
0x0000000000e0ce10 in void fc::divide<fc::uint128>(fc::uint128 const&, fc::uint128 const&, fc::uint128&, fc::uint128&) ()
(gdb) bt
#0  0x0000000000e0ce10 in void fc::divide<fc::uint128>(fc::uint128 const&, fc::uint128 const&, fc::uint128&, fc::uint128&) ()
#1  0x0000000000e0cf74 in fc::uint128::operator/=(fc::uint128 const&) ()
#2  0x0000000000c27b7c in graphene::chain::database::clear_expired_orders() ()
#3  0x0000000000c32a0b in graphene::chain::database::_apply_block(graphene::chain::signed_block const&) ()
#4  0x0000000000c337d5 in graphene::chain::database::apply_block(graphene::chain::signed_block const&, unsigned int) ()
#5  0x0000000000c33c90 in graphene::chain::database::_push_block(graphene::chain::signed_block const&) ()
#6  0x0000000000c35894 in graphene::chain::database::push_block(graphene::chain::signed_block const&, unsigned int) ()
#7  0x0000000000a8398f in graphene::app::detail::application_impl::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&) ()
#8  0x0000000000f71097 in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&)::{lambda()#1}>::run(void*, fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&)::{lambda()#1}>) ()
#9  0x0000000000e2bbc3 in fc::task_base::run_impl() ()
#10 0x0000000000e29d2e in fc::thread_d::process_tasks() ()
#11 0x0000000000e29fa1 in fc::thread_d::start_process_tasks(long) ()
#12 0x00000000010921c1 in make_fcontext ()
#13 0x0000000000000000 in ?? ()
http://cryptofresh.com  |  witness: roadscape

Offline abit

Re: Cryptofresh Block Explorer + MUSE now available
« Reply #119 on: January 07, 2016, 02:43:05 PM »
Sorry for the downtime guys, witness_node froze again.. bringing it back up..

Code: [Select]
798084ms th_a       application.cpp:497           handle_block         ] Got block: #2447427 time: 2016-01-07T08:13:18 latency: 85 ms from: maqifrnswa  irreversible: 2447408 (-19)
798264ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
799293ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
800307ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
800407ms th_a       application.cpp:546           handle_transaction   ] Got 1 transactions from network
801321ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
801345ms th_a       application.cpp:497           handle_block         ] Got block: #2447428 time: 2016-01-07T08:13:21 latency: 346 ms from: bitcube  irreversible: 2447408 (-20)
[stuck]
^C
Program received signal SIGINT, Interrupt.
0x0000000000e0ce10 in void fc::divide<fc::uint128>(fc::uint128 const&, fc::uint128 const&, fc::uint128&, fc::uint128&) ()
(gdb) bt
#0  0x0000000000e0ce10 in void fc::divide<fc::uint128>(fc::uint128 const&, fc::uint128 const&, fc::uint128&, fc::uint128&) ()
#1  0x0000000000e0cf74 in fc::uint128::operator/=(fc::uint128 const&) ()
#2  0x0000000000c27b7c in graphene::chain::database::clear_expired_orders() ()
#3  0x0000000000c32a0b in graphene::chain::database::_apply_block(graphene::chain::signed_block const&) ()
#4  0x0000000000c337d5 in graphene::chain::database::apply_block(graphene::chain::signed_block const&, unsigned int) ()
#5  0x0000000000c33c90 in graphene::chain::database::_push_block(graphene::chain::signed_block const&) ()
#6  0x0000000000c35894 in graphene::chain::database::push_block(graphene::chain::signed_block const&, unsigned int) ()
#7  0x0000000000a8398f in graphene::app::detail::application_impl::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&) ()
#8  0x0000000000f71097 in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&)::{lambda()#1}>::run(void*, fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&)::{lambda()#1}>) ()
#9  0x0000000000e2bbc3 in fc::task_base::run_impl() ()
#10 0x0000000000e29d2e in fc::thread_d::process_tasks() ()
#11 0x0000000000e29fa1 in fc::thread_d::start_process_tasks(long) ()
#12 0x00000000010921c1 in make_fcontext ()
#13 0x0000000000000000 in ?? ()
Is it started with --replay-blockchain? From my personal experience it won't hang by starting with this parameter.

//Edit: we have a discussion here https://bitsharestalk.org/index.php/topic,20631.0/all.html
« Last Edit: January 07, 2016, 02:45:21 PM by abit »
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

 

Google+