On Windows machine "Cron jobs" page does not load. The reason why is
$log_entry->start_time
in
src/CronJobListBuilder.php
returns scientific notation format, i.e. 1.46728e+09. Because of that, we get "The timestamp must be numeric." error while trying to open page.

CommentFileSizeAuthor
#6 ultimate_cron-n2762361-6.patch800 bytesDamienMcKenna
#3 2762361-3.patch803 bytesaudriusb
#2 2762361-2.patch796 bytesaudriusb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

audriusb created an issue. See original summary.

audriusb’s picture

audriusb CreditAttribution: audriusb commented
Status: Active » Needs review
FileSize
2762361-2.patch796 bytes
audriusb’s picture

audriusb CreditAttribution: audriusb commented
FileSize
2762361-3.patch803 bytes

New patch to fix "A non well formed numeric value encountered" introduced in previous patch.

audriusb’s picture

audriusb CreditAttribution: audriusb commented

although it sort of works, time in logs shows 1970 ... microtime() usage needs to be reviewed

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented
Status: Needs review » Needs work

Should have a space after (float).

sounds like it needs more work if the date isn't right?

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Needs work » Needs review
FileSize
ultimate_cron-n2762361-6.patch800 bytes

A minuscule fix for the spacing issue.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented
Priority: Critical » Minor
Status: Needs review » Closed (outdated)

No idea that's due to a mysql sql server or something, but as #4 said, you can't just convert that to a float if it's not.

apparently hasn't happened again in 7 years, so just closing that, feel free to reopen if it's still happening and can be properly fixed.