Re: 100 Push-Ups A Day Until Bitcoin Is $100K Challenge
>bigedit<
These days DirtyKeyboard might not even be manually reviewing his script every time that it runs, unless perhaps someone says something to him or if he might notice some kind of an obvious error. His script seems to mostly be getting the contents of the pushup reports into the pushup table in pretty accurate ways.
The script runs once a day at midnight UTC, so the script is ONLY going to take from pushup reports that have already been submitted prior to the running of the script (prior to midnight UTC), perhaps ONLY reviewing posts from the previous 24 hours. I am not sure if the script reviews the whole thread or just the last posts between the previous time that the script ran.
If you have not gotten your report in prior to the running of the script, then you have to wait until the next day (midnight UTC) for the script to run again for your results to be included in the script's reading and then putting the contents into the pushup's table. So you should want to fix any errors prior to the script's running..
To me, it looks like your report will be included in tomorrow's running of the script, yet when I look at your report again, you have put 2024-10-15 as your date, so if you want to submit another updated report prior to the running of the script tomorrow, you might want this report to show 2024-10-14 and your next report (if you make it prior to midnight UTC as 2024-10-15.. I am pretty sure that DirtyKeyboard's script will not recognize future dates (even if it is just one day), so when the script just ran a few hours ago, I believe that it might have ONLY allowed dates of up to 2024-10-14 and it would not have had recognized dates of 2024-10-15 or later. So if I understand the matter correctly, the next time that the script runs it will recognize dates that are up to 2024-10-15, but it will not recognize dates of 2024-10-16 or later. I am not 100% sure about that, but it does seem potentially problematic if you are putting the next day into your report even if you are already in the next day in terms of where you are at when DirtyKeyboard's script runs for everything in the previous day and earlier.
These days DirtyKeyboard might not even be manually reviewing his script every time that it runs, unless perhaps someone says something to him or if he might notice some kind of an obvious error. His script seems to mostly be getting the contents of the pushup reports into the pushup table in pretty accurate ways.
The script runs once a day at midnight UTC, so the script is ONLY going to take from pushup reports that have already been submitted prior to the running of the script (prior to midnight UTC), perhaps ONLY reviewing posts from the previous 24 hours. I am not sure if the script reviews the whole thread or just the last posts between the previous time that the script ran.
If you have not gotten your report in prior to the running of the script, then you have to wait until the next day (midnight UTC) for the script to run again for your results to be included in the script's reading and then putting the contents into the pushup's table. So you should want to fix any errors prior to the script's running..
To me, it looks like your report will be included in tomorrow's running of the script, yet when I look at your report again, you have put 2024-10-15 as your date, so if you want to submit another updated report prior to the running of the script tomorrow, you might want this report to show 2024-10-14 and your next report (if you make it prior to midnight UTC as 2024-10-15.. I am pretty sure that DirtyKeyboard's script will not recognize future dates (even if it is just one day), so when the script just ran a few hours ago, I believe that it might have ONLY allowed dates of up to 2024-10-14 and it would not have had recognized dates of 2024-10-15 or later. So if I understand the matter correctly, the next time that the script runs it will recognize dates that are up to 2024-10-15, but it will not recognize dates of 2024-10-16 or later. I am not 100% sure about that, but it does seem potentially problematic if you are putting the next day into your report even if you are already in the next day in terms of where you are at when DirtyKeyboard's script runs for everything in the previous day and earlier.
Here is the code that matches reports with a date
Code:
user, days_in, pushups_completed, report_date = match
if int(pushups_completed) >= 1:
if user not in latest_data or int(days_in) > int(latest_data[user][1]) and int(pushups_completed) > int(latest_data[user][2]) and report_date <= today2:
Basically comparing what is in the lastest record vs what is in that users latest report.if int(pushups_completed) >= 1:
if user not in latest_data or int(days_in) > int(latest_data[user][1]) and int(pushups_completed) > int(latest_data[user][2]) and report_date <= today2:
So to make the table the report needs at least 1 pushup, and be a brand new entrant OR repeat reporter with a greater days in, and a greater number of pushups, and the date is at least as current as yesterday UTC. In that case it would be picked up as a report with no optional date, and as you stated, be assigned the UTC date of the report. I think future dates should also be excluded as you alluded to. That seems pretty simple.
Surely editing your pushup report before the script runs would be ideal, and I think that the script is capable of correcting some mistakes in earlier pushup reports when it runs the next time, yet some kind of mistakes might need to be manually overridden.. such as if you were to put the days and the number of pushups in the wrong order.. then there might be some need for manual overriding... I am not exactly sure about which kinds of mistakes are more easily corrected, so it seems better to try not to make mistakes in your pushup reports (do a one over before submitting them). .. and so if you are mostly getting your reports correct now then, we wouldn't have to worry about you making future mistakes, until you do... hahahahaha.. cross that bridge when we get there.. or if we get there, no? Any of us could end up making a mistake, so there is that too..
Sure mistakes are inevitable, I'm currently at the top of the table 
...I guess I was the first to drop my entry yesterday. I am not sure. I was getting the impression that the script places the results into the table in reverse chronological order in terms of the top would be the person who submitted his pushup report the latest prior to the running of the script or if it is the last pushup report that the script reads prior to publishing the results in the pushup table.
All errors can be spotted easily though and the usage of scripts will definitely increase the chance of not getting it spotted, the script is more important while the error can always get corrected in the next entry by the poster but if spotted can also be corrected.
It probably was a lot of work to set up the script and then to make tweaks to the script, but now that it is running, it probably does not take as much work, unless some bug/glitch (or bad results) ends up getting spotted.
100k,JayJuanGee,255,57980,2024-10-16
The table is currently ranked by report date in local time [1], and in case of tie, number of new pushups, and in case of tie, person who reported first ever to the table. [1][not ideal, I think I remember some users having more new pushups but they reported in a totally acceptible yet non UTC date]
Report:100k,bigmanik,5,267,2024-10-17
Well
You don't need to add a " , " to a four digit or more Pu count Well
Good fortune to you and all.
My 8s are lucky Report: BTC100k,DirtyKeyboard,249,25688,2024-10-18BTC