{"action":"opened","issue":{"url":"https://api.github.com/repos/Automattic/Cron-Control/issues/42","repository_url":"https://api.github.com/repos/Automattic/Cron-Control","labels_url":"https://api.github.com/repos/Automattic/Cron-Control/issues/42/labels{/name}","comments_url":"https://api.github.com/repos/Automattic/Cron-Control/issues/42/comments","events_url":"https://api.github.com/repos/Automattic/Cron-Control/issues/42/events","html_url":"https://github.com/Automattic/Cron-Control/issues/42","id":193917245,"number":42,"title":"Limit how many `publish_future_post`, and other future, non-recurring events, are shown","user":{"login":"ethitter","id":321503,"avatar_url":"https://avatars.githubusercontent.com/u/321503?v=3","gravatar_id":"","url":"https://api.github.com/users/ethitter","html_url":"https://github.com/ethitter","followers_url":"https://api.github.com/users/ethitter/followers","following_url":"https://api.github.com/users/ethitter/following{/other_user}","gists_url":"https://api.github.com/users/ethitter/gists{/gist_id}","starred_url":"https://api.github.com/users/ethitter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ethitter/subscriptions","organizations_url":"https://api.github.com/users/ethitter/orgs","repos_url":"https://api.github.com/users/ethitter/repos","events_url":"https://api.github.com/users/ethitter/events{/privacy}","received_events_url":"https://api.github.com/users/ethitter/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-06T23:36:14Z","updated_at":"2016-12-06T23:36:14Z","closed_at":null,"body":"For non-recurring events, ones that Core and plugins won't try to reschedule, we can sometimes limit the size of the cron option and option cache by excluding items considerably outside of the event window. For example, the `publish_future_post` event for a post scheduled for next Thursday is rarely going to be relevant prior to next Thursday. This must be applied carefully, otherwise WordPress/the plugin will continually try to create an event entry. Fortunately, for predictable, non-recurring future events, the plugin's `job_exists()` method will prevent any attempt to introduce a duplicate event. The internal job for ensuring publish events exist will need to be updated."}}
{"actor":{"display_login":"ethitter"}}