-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default calendar losing events between backend and front end #3380
Comments
and it's repeatable. same event gets lost |
socketio uses json stringify before send, and parse on receive my traces do the same.. |
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. |
closing , can't reproduce |
this is happening again on 2.30 |
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 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) |
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) |
can you try safari or chrome? |
I'll note that the events do seem to eventually appear , although sometimes this takes several hours. |
yes, the socketio pipe is not connected for some reason |
Same behaviour with Safari and Firefox |
thanks |
any idea how to debug this? is socketio buffered? |
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]
The text was updated successfully, but these errors were encountered: