You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The actual issue was that one of the events ("Infrastructure Workshop Course Exhibition", May 12–17, id=5aecfb808c031300180f75f4) had an end date with sub-second accuracy (2018-05-17 03:59:59.999000), that Date.parse can't handle.
I've added a workaround to truncate the subseconds. (Not rounding, just because it's easier and I don't know where the fix should really go.)
osteele
changed the title
Events should be sorted
Events setup crashes on time with sub seconds
May 5, 2018
osteele
changed the title
Events setup crashes on time with sub seconds
events setup crashes on time with sub seconds
May 5, 2018
* Fix README markdown lint errors and typos
* Reorganize README; remove sudo from npm start
* Convert tabs to spaces in api.js
* Simplify the eslintrc
* Add travis config
* Lint the markdown
* Switch from npm to yarn
For consistency with abe-web. Also, because yarn is better :-).
* Lint js files in static
* Fix trivial lint errors
Semicolons, mixed spaces and tabs, one of the unused variables
* Add a Travis badge
* Fix lint errors in board_events.js
Since I'm going to be working here
* Teach server to display listening address in URL form, so I can click on it
* Workaround for #310 events setup crashes on time with sub seconds
* Update views url
* Add expo UI, Update video background to black
* Update css for expo UI
* Fix css error in upload.cscs
The event list at
/views/board
and/views/events
should be sorted by date.Multiday events should be sorted as though their start date were max(event.start, now.start_of_day).
The text was updated successfully, but these errors were encountered: