-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Overwritten recurrence with RRULESET when trying to sync with Gnome Evolution #112
Comments
Sorry for the slow reply! It got lost in my inbox :| Looking at what's going on, I suspect that you may have a malformed event. Luckily it shouldn't be too hard to figure it out.
Please let me know once you have more information, and sorry again for the delay. Please ping me on IRC/email the next time I'm taking too long to reply. |
No worries, I had forgotten about it myself a bit... but thanks for getting back to me! I found the entry, I'm attaching it below (renamed as a .txt file because github won't allow an ics). FYI I did try deleting it from my calendar (using my phone calendar app), but I still seem to be getting the same error. Let me know if there's anything else I can do on my end. |
Actually it looks like it might have just taken some time to sync, deleting the entry I attached above does allow me to setup my calendar in gnome evolution. I'm fine without that event in my calendar (was actually planning on removing it). But if there's anything else you need from me to look into this error more, just let me know. Thanks for the help! |
Glad to hear it works, I'll take a look at the event and try to figure it out. :) Just a funny thing I just noticed: the event's id starts with the word "bad". It was its destiny to fail. ;) |
I took a look at the file, and it looks fine to me. Additionally, I tried searching radicale for this error, and indeed this error doesn't seem relevant for this event. Here is the relevant ticket: Kozea/Radicale#700 |
Even crazier was that it was an event that was set to happen the day you got back to me.
Very weird... At least deleting it fixed it. Thanks again, I appreciate the help! Should I close this issue then? While the underlying cause wasn't really fixed, it's not really an issue anymore. |
There's some weird voodoo going on with this ticket. :P
I think I'll keep it open until I get a chance to properly investigate what is going on. Glad to hear we got it sorted out though. :) |
I got a similar issue. I'm trying to setup Evolution for the first time on Ubuntu 19.10. In Evolution I get the error "The reported error was “Failed to issue REPORT: HTTP error code 400 (Bad Request): Bad Request”.
|
It looks like exactly the same issue as discussed in both Kozea/Radicale#700 Looking there, it looks like you have an event with a recurrence-id although it's actually the main event, and not just one recurrence. The solution would be to remove the offending event from e.g. the web client. |
Thanks for your help! I managed to find out which calendar event was causing problem. Deleting the event solved it! I wasn't able to find the event through the debug link, so unfortunately I can't give you any more information. |
Ah damn, I was just going to say how much I love the debug link. :) Anyhow, if you deleted the event it should now be at the top of your journal, could you maybe share it (again, please anonymise as needed). |
Yes, you are right! I found the deleted event at the top of the journal. Here are the details of the event. Hope it can be of some use for you :)
|
Thanks for sharing. Interestingly enough, this event actually doesn't look wrong for all I see (assuming there's a related event with the full recurrence). |
I believe this is the first entry of the event. The strange thing is that this event is dated on 19-04-2014, while the event which caused problems was dated one month later at 19-05-2014. Maybe that is the reason the event couldn't be imported into Evolution?
I looked up the original event since it is imported from gmail. On gmail the event is dated on 19-05-2014 while it is supposed to recur every year on the 19th of April. This doesn't really make sense to me. So I guess gmail is the main source of the trouble here. |
Interesting. This event actually looks right too. One more thing you can check is: Do you see any other events with the same uid? |
I tried, but going to http://localhost:37358 simply redirects to http://localhost:37359, which is the management UI. |
Yeah, the management UI is on 37359 (though it changed in the latest version of etesync-dav!), though the 37358 (which is the main port) redirects there when you connect to the browser, so I always mention that one. Have you managed to find the event? |
I've investigated this further, and it seems to be an issue with events that have a |
When trying to use the bridge to add my calendar to gnome evolution, I get the following errors. The first error in the stack trace occurs when I try to 'find calendars' within evolution, but it does find the calendar just fine. The last error in the stack trace occurs when I try to refresh the calendar to actually get events. The calendar never actually gets the events for my calendar, and any time I try to refresh I get the same error regarding
Overwritten recurrence with RRULESET
, but I can't seem to find which event it might be causing this. I'm including the full stack trace as an attachment, which shows the first error I describe.etesync-dav.txt
The text was updated successfully, but these errors were encountered: