#109234Exclude PHP max_execution_time check from CLI environment reporting
Description
The latest patch 13.4.27 introduced CLI environment checks. (https://github.com/typo3/typo3/commit/03ee44a65cd)
The patch mentions, that some checks are disabled because of a different environment in CLI.
CLI comamands are often run without a `max_execution_time`. With the new change, this configuration is reported as a problem.
Reviews 2
Related issues 1
History 69
-
Garvin Hicking changed Related to #94365 <span data-processor="relativetime" data-value="2026-03-13T14:00:50+00:00" > 03/13/26, 14:00 </span>
-
Garvin Hicking commented and changed status
NewAccepted assigned to Garvin Hicking <span data-processor="relativetime" data-value="2026-03-13T14:02:23+00:00" > 03/13/26, 14:02 </span> -
Gerrit Code Review pushed patch set 1 for main to change 93192 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-03-15T00:01:59+00:00" > 03/15/26, 00:01 </span> -
Gerrit Code Review pushed patch set 2 for main to change 93192 <span data-processor="relativetime" data-value="2026-03-15T00:02:23+00:00" > 03/15/26, 00:02 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-03-15T00:02:41+00:00" > 03/15/26, 00:02 </span>
I’ve pushed a patch and would be happy for your review/feedback (=vote) :)
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 93235 <span data-processor="relativetime" data-value="2026-03-17T11:51:51+00:00" > 03/17/26, 11:51 </span>
-
Garvin Hicking commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-03-17T12:10:08+00:00" > 03/17/26, 12:10 </span>Applied in changeset commit:408d6b83656b72a572a336393b11a4353b2f8a08.
-
Garvin Hicking changed Duplicated by #109287 <span data-processor="relativetime" data-value="2026-03-19T06:33:54+00:00" > 03/19/26, 06:33 </span>
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T08:09:35+00:00" > 03/31/26, 08:09 </span>
Thanks for reporting this. I have to check if an unset limit should raise warnings at all. But at least I’ll try to exclude it from that report.