Calendar - Google sync bug (event duplication, external calendars)

Development
,
1

Hello,
My Google Calendar is connected to Gladys so that the events it contains are announced to me in advance by voice. The synchronization of one-off events works perfectly, but those that are recurring, whose end date has passed, continue to appear in Gladys’s calendar (and are therefore announced …).
Would a kind soul be willing to take a look at this?
Thanks,
Jean

2

If I’m not mistaken, it’s @bertrandda who’s in charge of this sort of thing!

1 Like
3

Hi @guim31

Thanks for this info :+1:

So, I’m adding two other observations I made today regarding the calendar:

  • I’ve connected an external calendar to my Google Calendar, and it doesn’t show up in Gladys,
  • I’ve removed external calendars
4

Hi Jean,

Indeed, I developed that part.

[quote=« jean_bruder, post:1, topic:9012 »]
The synchronization of one-off events works perfectly, but those that are recurring, with an expired end date, continue to appear in the Gladys (Gladys

3 Likes
5

Hello @bertrandda :slight_smile:

Thanks for addressing my request :+1:

The CalDAV sync for external calendars was indeed not enabled :sweat_smile: Maybe this should be mentioned in the Gladys documentation? I’ll confirm ASAP that everything is working properly!

Many thanks in the meantime :heart_eyes:
Jean

1 Like
6

Hello @bertrandda :slight_smile:

Have you had a chance to take a look at the reported issue?

Thanks,
Jean

7

Hi Jean, yes I submitted a PR with

1 Like
8

Hello, if you have mastery of the calendar part and not too much extra work in addition to the current request, could you see whether it’s possible to implement a solution where one can define the calendar

9

Yes, that should be doable :thinking:, I’ll do it later if that works for you.

1 Like
10

That’s it — I’ve added tests to fix the recurrence end issue.
A Docker image to try is available: bertrandda/gladys:caldav

The PR is here:

4 Likes
11

Great, thanks @bertrandda :slight_smile:

Is anyone planning to do a test?

12

Hello @pierre-gilles and @bertrandda :slight_smile:

If someone explains to me how to test, then roll back without losing anything from my current configuration, I’d be happy to!

Can I simply stop the current container and create a new one, with just the calendar configuration?

I’m available from 8:00 PM tonight if needed :slight_smile:

Have a nice day,
Jean

13

Hi @jean_bruder :slight_smile: That’s kind of you to offer.

I’m not sure today is the best day to do that — the DuckDB update will be released during the day, and if you tinker with your instance at the same time it’s not great.

What I suggest is that we wait for the DuckDB update to be released for everyone and for the migrations to have run, then @bertrandda you rebase your branch and rebuild the Docker image including DuckDB, and then we can run a test.

@bertrandda Can you confirm that your PR fixes the issue for existing installations?

14

Good evening,

I totally agree with you @pierre-gilles, one thing at a time :+1:

Have a nice evening,
Jean

1 Like
15

The build of the new image is in progress

it shouldn’t be able to fix the problems of calendars that are already synchronized since it won’t detect any changes on those. To fix those that already exist you must (with the new image) either use the ‹ reset › button and resynchronize everything or, if it’s for a particular calendar, go to the Synchronisation tab and disable the calendar, save and re-enable it.

2 Likes
16

Good evening @bertrandda and @pierre-gilles,

I confirm that after performing a resynchronization, all of the observed anomalies have been fixed :slight_smile:

Thank you very much,
Have a nice evening,
Jean

2 Likes
17

@jean_bruder did you test the new image then? :slight_smile:

18

Hello @pierre-gilles ,

I am on version 4.45.0, updated on August 26 following the switch to DuckDB

19

Ah ok, well that’s good that it helped with the existing data, but for the future it doesn’t solve the issue ^^

@bertrandda did you test your PR in production? If you’re confident it’s fine, I’ll just deploy what you did :slight_smile:

20

Indeed, to actually test the fix, you must :

  • create a recurring event with no recurrence end date
  • start synchronization in Gladys
  • add a recurrence end date
  • restart synchronization in Gladys
  • verify that events after the end of the recurrence have been removed from the Gladys calendar

I tested it in dev, it worked well, but additional tests with services other than the Nextcloud calendar would be a plus

1 Like