Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29306
11eb31b5 Fixed scheduler retrying publish jobs when there is nothing to publish The schedules publish endpoint returned a 404 when a job fired ahead of the scheduled time (because the post had been rescheduled to a later time) or when the post or page had since been deleted. External schedulers treat any non-2xx response as a failure and retry it, so these benign no-ops caused retry storms and noisy error logs that drown out real failures. Both cases now return a 2xx no-op so the job is treated as done. Firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing. The deleted case needs a custom permissions handler, because the permission stage loads the resource and 404s a missing one before the controller runs. It swallows only NotFoundError, so permission enforcement on resources that still exist is unchanged.
by Fabien O'C...
Succeeded
29306
1e29463d Fixed scheduler retrying publish jobs when there is nothing to publish The schedules publish endpoint returned a 404 when a job fired ahead of the scheduled time (because the post had been rescheduled to a later time) or when the post or page had since been deleted. External schedulers treat any non-2xx response as a failure and retry it, so these benign no-ops caused retry storms and noisy error logs that drown out real failures. Both cases now return a 2xx no-op so the job is treated as done. Firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing. The deleted case needs a custom permissions handler, because the permission stage loads the resource and 404s a missing one before the controller runs. It swallows only NotFoundError, so permission enforcement on resources that still exist is unchanged.
by Fabien O'C...
Succeeded
29306
295c3b91 Fixed scheduler retrying publish jobs when there is nothing to publish - the schedules publish endpoint returned a 404 when a job fired ahead of the scheduled time (the post was rescheduled later) or the post/page had been deleted - external schedulers treat any non-2xx as a failure and retry, so these benign no-ops caused retry storms and noisy error logs that drown out real failures - both cases now return a 2xx no-op so the job is treated as done; firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish - the deleted case needs a custom permissions handler, because the permission stage 404s a missing resource before the controller runs; it swallows only NotFoundError, so permission enforcement on resources that still exist is unchanged
by Fabien O'C...
Succeeded
29306
7a4177b3 Fixed scheduler retrying publish jobs when there is nothing to publish - the schedules publish endpoint returned a 404 in two cases where there is nothing to publish: the job fired ahead of the scheduled time (post rescheduled to a later time) or the post/page had since been deleted - schedulers treat any non-2xx as a failure and retry, so these benign no-ops caused retry storms and noisy error logs that drown out genuine failures - return a 2xx no-op for both cases so the job is treated as done; the deleted case needs a custom permissions handler, since the permission stage 404s a missing resource before the controller runs, and it tolerates only NotFoundError so permission enforcement on resources that exist is unchanged - firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing
by Fabien O'C...
Succeeded
29306
57a1bcd5 Fixed scheduler retrying publish jobs when there is nothing to publish - the schedules publish endpoint returned a 404 in two cases where there is nothing to publish: the job fired ahead of the scheduled time (post rescheduled to a later time) or the post/page had since been deleted - schedulers treat any non-2xx as a failure and retry, so these benign no-ops caused retry storms and noisy error logs that drown out genuine failures - return a 2xx no-op for both cases so the job is treated as done; the deleted case needs a custom permissions handler, since the permission stage 404s a missing resource before the controller runs, and it tolerates only NotFoundError so permission enforcement on resources that exist is unchanged - firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing
by Fabien O'C...
Succeeded
29306
5f023b30 Fixed scheduler retrying publish jobs that fire ahead of the scheduled time - when a post is rescheduled to a later time, a scheduler that can't invalidate the original job still fires it at the old, earlier time - the publish endpoint returned a 404 for that early fire, and schedulers retry any non-2xx, so it caused retry storms and noisy error logs that drown out genuine failures - return a 2xx no-op when a job fires ahead of its scheduled time so it is treated as done; firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish
by Fabien O'C...
Succeeded
29306
c2cc9762 Fixed scheduler retrying publish jobs that fire ahead of the scheduled time - when a scheduled post is rescheduled to a later time, a scheduler that cannot invalidate the original job still fires it at the old, earlier time - the publish endpoint returned 404 for that early fire, and schedulers treat non-2xx as a failure and retry, causing retry storms and noisy error logs that drown out genuine failures - return a 2xx no-op when the job fires ahead of the scheduled time, so it is treated as done - firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing
by Fabien O'C...
Failed
29306
756efc45 Fixed scheduler retrying publish jobs when there is nothing to publish - the schedules publish endpoint returned 404 when a scheduled post was deleted, already unscheduled, or fired ahead of its scheduled time (e.g. a stale job for a post that was later rescheduled) - some scheduler implementations treat any non-2xx as a failure and retry, so these benign no-ops caused retry storms and noisy error logs even though the scheduler had done its job by reaching us - return a 2xx no-op (empty resource list) for those cases so the job is treated as done - firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing
by Fabien O'C...
Failed
29306
a848b335 Fixed scheduler retrying publish jobs when there is nothing to publish - the schedules publish endpoint returned 404 when a scheduled post was deleted, already unscheduled, or fired ahead of its scheduled time (e.g. a stale job for a post that was later rescheduled) - some scheduler implementations treat any non-2xx as a failure and retry, so these benign no-ops caused retry storms and noisy error logs even though the scheduler had done its job by reaching us - return a 2xx no-op (empty resource list) for those cases so the job is treated as done - firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing
by Fabien O'C...