MAJOR OUTAGE caused by daylight saving bug
Posted: 28 December 2020, 02:13
Both production BGA and studio are totally broken right now because of the following error. Looks like this SQL runs when I try to login or start a table in studio (maybe also at every move? but I can't get that far to test).
Google says Daylight saving time 2021 in Europe will begin at 1:00 AM on Sunday, March 28 so the error happens because now + 3 months results in a time that doesn't exist. Using DATE_ADD() apparently is not safe, unless you set the MySQL database's timezone to UTC (so there's no daylight saving involved).
Google says Daylight saving time 2021 in Europe will begin at 1:00 AM on Sunday, March 28 so the error happens because now + 3 months results in a time that doesn't exist. Using DATE_ADD() apparently is not safe, unless you set the MySQL database's timezone to UTC (so there's no daylight saving involved).
Code: Select all
Unexpected error: Error while processing SQL request (Localhost via UNIX socket): INSERT INTO l_catchup_email_metrics (lcm_user_id, lcm_next_send_time) VALUES (2305326, DATE_ADD(NOW(), INTERVAL 3 MONTH)) ON DUPLICATE KEY UPDATE lcm_next_send_time = VALUES(lcm_next_send_time)
Incorrect datetime value: '2021-03-28 02:01:27' for column 'lcm_next_send_time' at row 1