Skip to content
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

OGCS does not complete - seems to hang #2024

Open
mjlipton opened this issue Dec 10, 2024 · 2 comments
Open

OGCS does not complete - seems to hang #2024

mjlipton opened this issue Dec 10, 2024 · 2 comments
Labels
bug Something's not working right

Comments

@mjlipton
Copy link

Checklist:-

  • Upgrade to the latest release (alpha if available) latest release
  • Reproduce the issue
  • Complete the information below
  • Provide your OGcalsync.log file (see how-to)

OGCS Version: v2.11.1.0
Edition: Installed
Sync Direction: G->O

Bug Description

OGCS fails to complete after starting g->o phase. have waited overnight for completion with no result.

Steps to Reproduce the Issue

  1. Run OGCS

Any other information
this may or may not be related, but previously I was getting some weird error messages on certain events that there was "extended private data" on certain Google events (birthdays). I have not done anything fancy with respect to birthdays. So, in order to make this error go away, I unclicked the "Birthday" calendar type in Google to make all the birthdays go away.

OGcalsync.log

@mjlipton mjlipton added the bug Something's not working right label Dec 10, 2024
@mjlipton
Copy link
Author

I have gotten OGCS to work now, by doing a series of one-way syncs to delete items in each calendar that originated on the other side, and then doing a bidirectional sync. So my urgent issue is over, but whatever happened may be of concern to you.

@phw198
Copy link
Owner

phw198 commented Dec 15, 2024

The issue looks to be to a possibly spurious m appointment with 6570 exceptions to the recurring series - so it was trying to iterate them all. I've no idea what causes all these exceptions, but I have seen it a handful of times before.

2024-12-10 12:03:41,751 DEBUG 12 OutlookGoogleCalendarSync.Outlook.Calendar [440] -  7/1/2021 10:00 AM (R) => "m"
2024-12-10 12:03:41,753 DEBUG 12 OutlookGoogleCalendarSync.Recurrence [411] -  This is a recurring Google event with 6570 exceptions in the sync date range.

If that item was on your Birthday calendar, then excluding that whole calendar will have worked around the issue. Equally, you could delete that m series and then bring that calendar back in scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's not working right
Projects
None yet
Development

No branches or pull requests

2 participants