fix(07-02): MariaDB TIMESTAMP format in global-setup seed
- Replace ISO 8601 'T' separator with space in dtstart_utc value - MariaDB TIMESTAMP requires 'YYYY-MM-DD HH:MM:SS', not 'YYYY-MM-DDTHH:MM:SSZ' - Was causing 'Incorrect datetime value' error blocking all e2e harness runs
This commit is contained in:
@@ -75,7 +75,11 @@ export default async function globalSetup(): Promise<void> {
|
|||||||
// Uses a future dtstart_utc so the event is visible in the UI's default "upcoming" view.
|
// Uses a future dtstart_utc so the event is visible in the UI's default "upcoming" view.
|
||||||
const uid = 'e2e-seed-event-001'
|
const uid = 'e2e-seed-event-001'
|
||||||
const futureStart = new Date(Date.now() + 24 * 60 * 60 * 1000) // tomorrow UTC
|
const futureStart = new Date(Date.now() + 24 * 60 * 60 * 1000) // tomorrow UTC
|
||||||
const futureStartUtc = futureStart.toISOString().replace(/\.\d+Z$/, 'Z') // trim ms
|
// MariaDB TIMESTAMP requires 'YYYY-MM-DD HH:MM:SS' format, not ISO 8601 with 'T'.
|
||||||
|
const futureStartUtc = futureStart
|
||||||
|
.toISOString()
|
||||||
|
.replace('T', ' ')
|
||||||
|
.replace(/\.\d+Z$/, '')
|
||||||
const rawVevent = [
|
const rawVevent = [
|
||||||
'BEGIN:VCALENDAR',
|
'BEGIN:VCALENDAR',
|
||||||
'VERSION:2.0',
|
'VERSION:2.0',
|
||||||
|
|||||||
Reference in New Issue
Block a user