Contrib.social

CronFrequencyValidator should not check if updates will be run via console

Open on Drupal.org →
Created on 19 July 2023, over 1 year ago
Updated 20 July 2023, over 1 year ago

Problem/Motivation

Discovered 📌 For web server dependent unattended updates run the entire life cycle in a separate process that will not be affected by hosting time limits Fixed and makes this hard to test because when terminal multiple times with delays(because still don't run status checks more than 1x hour) this CronFrequencyValidator will start to error if you delay too long.

but the whole purpose CronFrequencyValidator is to ensure that updates and status checks will be run. but if you select "console" this will not happen via cron anyways so it is not valid check.

If you select "console" to run updates you should be able to run cron 1x day or less if that is all you need otherwise

Steps to reproduce

Exit early in CronFrequencyValidator if "console" method has been chosen to run updates

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Fixed

Version

3.0

Component

Code

Created by

🇺🇸United States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024