bug PR-6.2-dev Pending

User tests: Successful: Unsuccessful:

avatar krishnagandhicode
krishnagandhicode
22 Oct 2026

Pull Request resolves # .

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

while running long (translation task from gsoc project) tasks on a site, I noticed that some runs were missing from Execution History.

The duration column of #__scheduler_logs is DECIMAL(5,3), so it can only hold up to 99.999 seconds. when a run takes 100 seconds or more saving its Execution History row fails and the error gets ignored. The task itself runs fine and its last run and exit code are updated but the run never shows up in the execcu history. This happens for both successful and failed runs.

This PR widens the column to DECIMAL(8,3) (NUMERIC(8,3) on PostgreSQL) in the install SQL and allso adds update files for existing sites.

Testing Instructions

You can use any long scheduled task that should take more than 99.999 seconds for it's execution.

Or we create a situation like that by:
1 Create a file sleep.php in the site root:

<?php
set_time_limit(0);
sleep(105);
echo 'ok';

2 then go to System -> Manage -> Scheduled tasks -> New > search and select "GET Request".
Configure it by giving an title and use URL: https://<your site>/sleep.php and leave the Request Timeout at 120. now Save&Close.

3 Click Run task on the new task. It takes about 105 seconds.
4 Open Execution History - look at rows (before and after of this PR)

Note : Apply the PR, then make sure to update DB by:
System -> Maintenance -> Database --> Update Structure, and run the task again.

Actual result BEFORE applying this Pull Request

The task finishes successfully after about 105 seconds, but Execution History shows no entry for the run.

Expected result AFTER applying this Pull Request

The run appears in Execution History with a duration of about 105 seconds.

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:

  • No documentation changes for guide.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

avatar krishnagandhicode krishnagandhicode - open - 22 Oct 2026
avatar krishnagandhicode krishnagandhicode - change - 22 Oct 2026
Status New ⇒ Pending
avatar joomla-cms-bot joomla-cms-bot - change - 22 Oct 2026
Category ⇒ SQL Administration com_admin Postgresql Installation
avatar krishnagandhicode krishnagandhicode - change - 22 Oct 2026
The description was changed
avatar krishnagandhicode krishnagandhicode - edited - 22 Oct 2026
avatar krishnagandhicode
krishnagandhicode - comment - 22 Oct 2026

Thanks @brianteeman, I looked into it: CAN FAIL is meant for statements that would fail when run again, like for adding a column that already exists (see point 2 in the summary of #37156). MODIFY can run again without an error. I ran this update file twice through the installer and the second run went through fine. (also tried an ADD COLUMN without the marker, which failed on its second run.)

Core's existing MODIFY statements don't use it either - So i believe we keep it as is ?

avatar brianteeman
brianteeman - comment - 22 Oct 2026

ok

avatar alikon
alikon - comment - 23 Oct 2026

it's a bit too much With NUMERIC(10,3) 9,999,999.999 seconds you get: ~115 days

avatar krishnagandhicode
krishnagandhicode - comment - 23 Oct 2026

it's a bit too much With NUMERIC(10,3) 9,999,999.999 seconds you get: ~115 days

ahh fair point.
would DECIMAL(7,3) : about 2.8 hours OR DECIMAL(8,3) : about 27 ? (Not sure if we need that much too)

avatar krishnagandhicode
krishnagandhicode - comment - 23 Oct 2026

it's a bit too much With NUMERIC(10,3) 9,999,999.999 seconds you get: ~115 days

ahh fair point.
would DECIMAL(7,3) : about 2.8 hours be fine OR DECIMAL(8,3) : about 27 ? (Not sure if we need that much too)

avatar alikon
alikon - comment - 23 Oct 2026

maybe DECIMAL(8,3) should be enough

avatar krishnagandhicode krishnagandhicode - change - 23 Oct 2026
Labels Added: bug PR-6.2-dev
avatar krishnagandhicode
krishnagandhicode - comment - 23 Oct 2026

maybe DECIMAL(8,3) should be enough

done.

avatar krishnagandhicode krishnagandhicode - change - 23 Oct 2026
The description was changed
avatar krishnagandhicode krishnagandhicode - edited - 23 Oct 2026
avatar alikon alikon - test_item - 23 Oct 2026 - Tested successfully
avatar alikon
alikon - comment - 23 Oct 2026

I have tested this item ✅ successfully on e45e5ba


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48682.

avatar alikon
alikon - comment - 23 Oct 2026

I have tested this item ✅ successfully on e45e5ba


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48682.

avatar exlemor exlemor - test_item - 23 Oct 2026 - Tested successfully
avatar exlemor
exlemor - comment - 23 Oct 2026

I have tested this item ✅ successfully on e45e5ba

During Happy Friday PR Testing, I was able to test this successfully! Thanks @krishnagandhicode!


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48682.

avatar exlemor
exlemor - comment - 23 Oct 2026

I have tested this item ✅ successfully on e45e5ba

During Happy Friday PR Testing, I was able to test this successfully! Thanks @krishnagandhicode!


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48682.

avatar alikon alikon - change - 24 Oct 2026
Status Pending ⇒ Ready to Commit
avatar alikon
alikon - comment - 24 Oct 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48682.

avatar alikon
alikon - comment - 24 Oct 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48682.

Add a Comment

Login with GitHub to post a comment