default calendar losing events between backend and front end

[sdetweil]

see

https://forum.magicmirror.builders/topic/18325/calendar-not-updating/85?_=1706893005707

I have added traces to just before the socketsend from node helper and traces to the front end, and the event shows before send, and does not show after socket receive

the event is NOT at the start or end of the data

how else can I debug this?

we just did a new npm install, on 2.26, with [email protected]

[sdetweil]

and it's repeatable. same event gets lost

[sdetweil]

socketio uses json stringify before send, and parse on receive

my traces do the same..

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[sdetweil]

closing , can't reproduce

[sdetweil]

this is happening again on 2.30
https://forum.magicmirror.builders/post/123493
only thing we changed here was the socketio setup

[emlowe]

I appear to be having this issue:

I added various log outputs to node_helper.js and calendar.js

node_helper is sending the socket notification for CALENDAR_EVENTS
this is not received by the front-end code in calendar.js

I don’t know what happens to it, but I added logging to print out in calendar.js whenever the socketNotificationReceived handler is called and it doesn’t print.

(unless I refresh the page - at which point it does)

[emlowe]

I have seen this behavior in both server mode and with normal electron mode. Most of my recent debugging is in server mode so I can bring up the webpage in a different browser on a second machine

Current test environment:

rpi3 with Debian GNU/Linux 12 (bookworm)
Running develop branch of MM with node v22.13.0
Front-end on Brave browser on a mac

[sdetweil]

can you try safari or chrome?

[emlowe]

I'll note that the events do seem to eventually appear , although sometimes this takes several hours.

[sdetweil]

yes, the socketio pipe is not connected for some reason

[emlowe]

Same behaviour with Safari and Firefox

[sdetweil]

thanks

[sdetweil]

any idea how to debug this? is socketio buffered?

[sdetweil]

maybe the buffer size isn't big enough

change server.js
add the line marked below

			const io = socketio(server, {
				cors: {
					origin: /.*$/,
					credentials: true
				},
				allowEIO3: true,                // add this trailing comma
				maxHttpBufferSize: 1e7   // add this line, set buffer to 10 meg max from 1 meg
			});

[emlowe]

I tried this and it didn't seem to make any difference (I tried 1e8 since that is the WS default). I also added some error logging

socket.on("error", (err) => {
	console.error(`Socket error: ${err.message}`);
});

but nothing gets logged so it doesn't seem there is an error being thrown.

[sdetweil]

thanks. the default i saw was 1e6, 1meg

as i understand it there is no error reported its just lost

https://socket.io/docs/v4/troubleshooting-connection-issues/

other thing was to change the timeout, but that didn't seem appropriate

[sdetweil]

hit button on phone