I had an event in my calendar that ended in a time that did not exist! TV and stuff was set to go off at 2am, even on the day the clocks went forward, and that time does not exist. The time leaps straight from 1am to 2am and a microsecond or something like that. So could not turn the tv off in a time that did not exist and everything crashed out. Have caught that error and all is good again now.
The dining room light just came on which is my early warning I should go to bed soon, but I'm still working on my new idea of converting ical to crontab... If I'd done this previously then a) I wouldn't have to query the calendar every minute to see if there's a new event and b) all the repeating events would just keep going even when the internet goes down. I think this is going to be a good one...
Paul Clarke's blog - I live in Hythe in Kent. Married to Clare + father to two, I am a full-stack web engineer, + I do javascript / nodejs, some ruby, python, php ect ect. I like pubbing, running, eating, home automation and other diy jiggery-pokery, history, genealogy, TV, squirrels, pirates, lego, and TIME TRAVEL.