Sascha Foerster
03/20/2022, 8:19 AM@calcom/web:dev: 09:16:02.047 timeZoneName WARN CalendarManager
@calcom/web:dev: at new ParserError (/home/cal.com/node_modules/ical.js/build/ical.js:1756:13)
@calcom/web:dev: at Object.parser [as parse] (/home/cal.com/node_modules/ical.js/build/ical.js:1794:13)
@calcom/web:dev: at eval (webpack-internal:///(api)/./lib/integrations/calendar/services/BaseCalendarService.ts:201:77)
@calcom/web:dev: at Array.map (<anonymous>)
@calcom/web:dev: at CalDavCalendarService.getAvailability (webpack-internal:///(api)/./lib/integrations/calendar/services/BaseCalendarService.ts:200:11)
@calcom/web:dev: at runMicrotasks (<anonymous>)
@calcom/web:dev: at processTicksAndRejections (internal/process/task_queues.js:95:5)
@calcom/web:dev: at async Promise.all (index 0)
@calcom/web:dev: at async getBusyCalendarTimes (webpack-internal:///(api)/./lib/integrations/calendar/CalendarManager.ts:122:19)
@calcom/web:dev: at async handler (webpack-internal:///(api)/./pages/api/availability/[user].ts:86:23) {
@calcom/web:dev: message: 'invalid ical body. component began but did not end'
@calcom/web:dev: }
Shall I create a new issue? Or is it probably a Kerio issue?zomars
04/12/2022, 3:14 PMSascha Foerster
04/15/2022, 9:43 PM2|calcom | @calcom/web:start: 21:38:39.651 timeZoneName WARN CalendarManager
2|calcom | @calcom/web:start: at new ParserError (/home/cal.com/node_modules/ical.js/build/ical.js:1756:13)
2|calcom | @calcom/web:start: at Object.parser [as parse] (/home/cal.com/node_modules/ical.js/build/ical.js:1794:13)
2|calcom | @calcom/web:start: at /home/cal.com/apps/web/.next/server/chunks/3372.js:6252:77
2|calcom | @calcom/web:start: at Array.forEach (<anonymous>)
2|calcom | @calcom/web:start: at CalDavCalendarService.getAvailability (/home/cal.com/apps/web/.next/server/chunks/3372.js:6250:17)
2|calcom | @calcom/web:start: at runMicrotasks (<anonymous>)
2|calcom | @calcom/web:start: at processTicksAndRejections (internal/process/task_queues.js:95:5)
2|calcom | @calcom/web:start: at async Promise.all (index 0)
2|calcom | @calcom/web:start: at async getBusyCalendarTimes (/home/cal.com/apps/web/.next/server/chunks/6477.js:105:19)
2|calcom | @calcom/web:start: at async handler (/home/cal.com/apps/web/.next/server/pages/api/availability/[user].js:517:23)
2|calcom | @calcom/web:start: at async Object.apiResolver (/home/cal.com/node_modules/next/dist/server/api-utils/node.js:184:9)
2|calcom | @calcom/web:start: at async NextNodeServer.runApi (/home/cal.com/node_modules/next/dist/server/next-server.js:395:9)
2|calcom | @calcom/web:start: at async Object.fn (/home/cal.com/node_modules/next/dist/server/base-server.js:477:37)
2|calcom | @calcom/web:start: at async Router.execute (/home/cal.com/node_modules/next/dist/server/router.js:243:32)
2|calcom | @calcom/web:start: at async NextNodeServer.run (/home/cal.com/node_modules/next/dist/server/base-server.js:594:29)
2|calcom | @calcom/web:start: at async NextNodeServer.handleRequest (/home/cal.com/node_modules/next/dist/server/base-server.js:299:20) {
2|calcom | @calcom/web:start: message: 'invalid ical body. component began but did not end'
2|calcom | @calcom/web:start: }
Sascha Foerster
04/16/2022, 11:12 AMSascha Foerster
07/11/2022, 10:57 PM