-
Notifications
You must be signed in to change notification settings - Fork 168
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
Pending Caldav Issues #909
Comments
Hi, the caldav backend could definitely use more testing. I would suggest not jumping in yet, as the whole backends system is going to be heavily changed in #894 . If you want to get familiar with the code, you can start reading: https://github.com/getting-things-gnome/gtg/blob/master/GTG/backends/backend_caldav.py GTG always keeps several backups so it's hard to lose data though. |
Hey @diegogangl. Thanks! Your work on PR #894 looks great and I'm really excited for it. I have a few questions. After this PR, will the Caldav backend need to be rewritten? Will the updated caldav backend be part of this PR or will someone else have to tackle it once you're done with this? Do you know how far off we are from working on these issues? (not asking for any commitment, of course. Just want a rough idea). Asking these questions since if the backend system will be undergoing only minor changes and if the PR is still too far out, it might be worth just fixing them now and then porting them over to the new system. |
Any idea when caldav backend can start working? Or what needs to happen in order to get this to work? I am happy to chip in and spend hours working on this if anyone is willing to guide me and point in the right direction. |
The big merge has happened, #737's description has been updated to reflect the status of everything, and provides convenient links to a filtered and sorted search for all CalDAV issues, I think we can close this ticket now. |
When all (or as much as possible) of the "regression"-labelled and/or "0.7-targetted" issues mentioned in #737 are fixed. With some luck and lots of community involvement, this can happen pretty quickly, I would think. |
I just started using gtg with caldav for sync and I started noticing a bunch of issues. Tasks that I had added would suddenly get deleted and subtasks would not get synced correctly. After doing some digging, it looks like these are known issues: #525 (comment)
and
#892
I would suggest maybe marking the sync service as experimental until we can figure out a solution to these. I haven't worked with the codebase before, so if someone more familar with the codebase knows where to start, I would be happy to contribute fixes for these myself.
I was lucky enough to have a backup of all the tasks that gtg deleted for me, however I can imagine it being pretty frustrating if gtg ended up deleting your tasks that you spent a lot of time writing.
The text was updated successfully, but these errors were encountered: