kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
January 27, 2016, 07:36:07 AM |
|
Anyone that signed up after 2015-01-14 may have not gotten the last block notification and will be missing hashrate on their graph from 12:20 pm EST to 7:52 pm EST. A user accidentally had a space after their username and the process that runs to get all the data was dieing at that point. I believe I have fixed this so it won't happen again. Until the next unforeseen issue arises things are working again. There's allowed to be a space in the username (but they get stripped off the front and end) I of course never disallowed that, but also never had one before until recently when one of my scripts failed to work processing a payout at home
|
|
|
|
ZACHM (OP)
|
|
January 27, 2016, 08:03:26 PM |
|
There's allowed to be a space in the username (but they get stripped off the front and end) I of course never disallowed that, but also never had one before until recently when one of my scripts failed to work processing a payout at home Are you saying that I need to make sure that my script can safely process usernames that could have a space in the middle of them? I guess I'll implement that either way, but having usernames with spaces just seems silly. I had just set it to strip spaces for now, but I will now just trim them from the ends and I will have to add a % (I assume) if there is a space in the middle so the api will still work? It is fun hitting these little things and thinking wow I didn't see that one coming , then you have to find the solution.
|
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
January 27, 2016, 09:27:41 PM |
|
There's allowed to be a space in the username (but they get stripped off the front and end) I of course never disallowed that, but also never had one before until recently when one of my scripts failed to work processing a payout at home Are you saying that I need to make sure that my script can safely process usernames that could have a space in the middle of them? I guess I'll implement that either way, but having usernames with spaces just seems silly. I had just set it to strip spaces for now, but I will now just trim them from the ends and I will have to add a % (I assume) if there is a space in the middle so the api will still work? It is fun hitting these little things and thinking wow I didn't see that one coming , then you have to find the solution. There's an item on my todo list to add a value to the API call "usercode" as a hex version of the username and show that on the web page. But it will continue to support both Sooner or later I need to get the main pool to properly support UTF-8 (it works at home but not on the live pool - basically just a postgresql or apache setting I got wrong somewhere )
|
|
|
|
ZACHM (OP)
|
|
January 28, 2016, 02:32:18 AM |
|
There's an item on my todo list
I can only image the length of your todo list. I know mine is very long if you include my job and my wife's list for me. Here is a teaser screen shot for those interested in V2 of the monitor. Let me know what other "gauges" or information I should try to show. I plan on getting current block and network difficulty on there.
|
|
|
|
marvykkio
|
|
January 29, 2016, 06:55:15 AM |
|
I like this graphic, much easier
|
|
|
|
ZACHM (OP)
|
|
January 30, 2016, 04:29:23 AM |
|
V2 is live! Let me know if you find anything that is not working. I am going through things, and I think I have most of the transition issue solved. I am planning on moving the hashing graphs to the dashboard. They will be smaller with less detail and a shorter timespan, but you will be able to click on them (or link nearby) to go to a full size same as it is now. Also planning on making the hashgraph for the overall pool on the main page load faster.
|
|
|
|
kipper01
Full Member
Offline
Activity: 214
Merit: 100
1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ
|
|
January 30, 2016, 01:50:22 PM |
|
V2 is live! I am liking it! One question would it make more sense on the reward page to flip them? Show newest block first?
|
|
|
|
ZACHM (OP)
|
|
January 30, 2016, 01:54:33 PM |
|
Yes, I was planning on making it an option, so people can see it the way they want. Soon...
|
|
|
|
cryptotore
|
|
January 30, 2016, 02:16:35 PM |
|
Thanks for your efforts, appreciated!
|
|
|
|
clgrissom3
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
January 30, 2016, 05:00:24 PM |
|
V2 is very nice! Keep it going!
|
|
|
|
zOU
|
|
January 30, 2016, 05:35:56 PM |
|
Thank you !
is there a possibility we could change/set the timezone for the graph ?
|
|
|
|
ZACHM (OP)
|
|
January 30, 2016, 05:36:54 PM |
|
That is on the to-do list.
|
|
|
|
zOU
|
|
January 30, 2016, 05:47:19 PM |
|
That is on the to-do list. Correct, my apologies, I was just about to edit my post... ++>> - Users have option between local time and UTC (Pool Time) on the graphs, etc.
|
|
|
|
|
cryptotore
|
|
January 30, 2016, 06:18:56 PM |
|
Found a small bug in the reward view range when converting btc to NOK. https://i.imgur.com/W7BpUGv.png0.6 btc = 226 usd = 1961 nok Seems like it is counting 0.05 btc as 0.5 btc or something like that. Thanks.
|
|
|
|
zOU
|
|
January 30, 2016, 06:42:16 PM |
|
Something strange is displayed: the graph starts 7h ago, even though I've joined the pool only slightly over 1h ago... or I don't read it correctly ? Also, I do not really understand the peaks in hash rate...1mn I have 0Ghs reported, the following update is ok (1.3THs) etc etc
|
|
|
|
ZACHM (OP)
|
|
January 30, 2016, 06:45:56 PM |
|
I am not at home right now (on my phone). I'll look into all of this when I get home. Sorry I can't get to it right away.
|
|
|
|
zOU
|
|
January 30, 2016, 06:59:45 PM Last edit: January 31, 2016, 06:34:27 AM by zOU |
|
I am not at home right now (on my phone). I'll look into all of this when I get home. Sorry I can't get to it right away.
no worries, I'll be happy to know what I'm reading wrong (or to help you noticing something unusual) when you get the time. Editing to insert a better capture:
|
|
|
|
ZACHM (OP)
|
|
January 30, 2016, 09:06:10 PM |
|
Found a small bug in the reward view range when converting btc to NOK. https://i.imgur.com/W7BpUGv.png0.6 btc = 226 usd = 1961 nok Seems like it is counting 0.05 btc as 0.5 btc or something like that. Thanks. I'll have to check on this on the computer later tonight. Not sure what is going on, must be an issue converting from USD to NOK. no worries, I'll be happy to know what I'm reading wrong (or to help you noticing something unusual) when you get the time.
I think I have this fixed. It is a timezone issue I noticed last night but didn't get a chance to fix yet. I think yours is fixed too, let me know.
|
|
|
|
Gornidah
Member
Offline
Activity: 111
Merit: 10
|
|
January 30, 2016, 09:13:45 PM |
|
Yeah, its fine now, thanks!
|
|
|
|
|