![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archives
|
2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 |
While DYKUpdateBot usually works like a champ, from time to time something will happen that prevents the bot from performing its job at its normal time interval. This has the effect of altering not just the time when the affected update occurs but the time for all subsequent updates as well. As it is often convenient and desirable to have an update occur at 00:00 UTC (midnight) it would be nice if DYKUpdateBot could detect when some form of delay has occurred and automatically take appropriate actions to resync over time.
What I envision is DYKUpdateBot performing an extra check at each update to determine if things are scheduled in such a manner that either the current or an upcoming update will occur at midnight. If not, a small addition or subtraction to the time between updates will be made by the bot to allow for a resync to be made over the course of time. A new configuration value (MaxAdjustmentValue) would control the maximum adjustment the bot can perform during a single update. Setting MaxAdjustmentValue to a positive value would allow the bot to increase the time between each update by the indicated number of seconds while a negative value to the configuration value would authorize the bot to reduce the time between updates by a like amount. When an adjustment less the the maximum needed is required, the bot should obviously calculate the needed offset and use only the needed offset. A setting of zero should disable the feature for cases when synchronized operations are desirable or the time between updates has been set to a value that does not allow for midnight updates to occur on a daily basis.
This is obviously just a "nice to have", so no pressure if you have no interest in making this addition. -- Allen3 talk 14:20, 3 March 2011 (UTC)
I see that you are away but if you see this you might want to look at DYKHousekeepingBot, Did you know/DYK hook count hasn't updated in nearly a week. Take care, J04n( talk page) 02:11, 20 March 2011 (UTC)
See [1]. IIRC both of those appeared in the same queue - could be the reason. -- Piotr Konieczny aka Prokonsul Piotrus| talk 15:15, 6 April 2011 (UTC)
diff. cmadler ( talk) 16:15, 28 April 2011 (UTC)
![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archives
|
2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 |
While DYKUpdateBot usually works like a champ, from time to time something will happen that prevents the bot from performing its job at its normal time interval. This has the effect of altering not just the time when the affected update occurs but the time for all subsequent updates as well. As it is often convenient and desirable to have an update occur at 00:00 UTC (midnight) it would be nice if DYKUpdateBot could detect when some form of delay has occurred and automatically take appropriate actions to resync over time.
What I envision is DYKUpdateBot performing an extra check at each update to determine if things are scheduled in such a manner that either the current or an upcoming update will occur at midnight. If not, a small addition or subtraction to the time between updates will be made by the bot to allow for a resync to be made over the course of time. A new configuration value (MaxAdjustmentValue) would control the maximum adjustment the bot can perform during a single update. Setting MaxAdjustmentValue to a positive value would allow the bot to increase the time between each update by the indicated number of seconds while a negative value to the configuration value would authorize the bot to reduce the time between updates by a like amount. When an adjustment less the the maximum needed is required, the bot should obviously calculate the needed offset and use only the needed offset. A setting of zero should disable the feature for cases when synchronized operations are desirable or the time between updates has been set to a value that does not allow for midnight updates to occur on a daily basis.
This is obviously just a "nice to have", so no pressure if you have no interest in making this addition. -- Allen3 talk 14:20, 3 March 2011 (UTC)
I see that you are away but if you see this you might want to look at DYKHousekeepingBot, Did you know/DYK hook count hasn't updated in nearly a week. Take care, J04n( talk page) 02:11, 20 March 2011 (UTC)
See [1]. IIRC both of those appeared in the same queue - could be the reason. -- Piotr Konieczny aka Prokonsul Piotrus| talk 15:15, 6 April 2011 (UTC)
diff. cmadler ( talk) 16:15, 28 April 2011 (UTC)