CalDAV sync malfunctioning (server issue)

Open
#281 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start by reviewing the linked server issue #146 and the EteSync DAV sync entry points that handle CalDAV/CardDAV requests. Reproduce the reported intermittent HTTP 500 response and trace whether the failure originates in this adapter or the server. Done means identifying the cause and resolving the repeated sync failures without losing calendar events.

Written by the indexing model from the issue text.

Description

For the past several hours the CalDAV sync has been going in and out of normal function, causing events on my calendar to disappear and re-appear continually. One event I tried to add this afternoon disappeared after one of these sync fluctuations.

This seems to be caused by a server side issue. Is there an ETA on a fix?

My calendar application reports this error repeatedly:
[CalDAV / CardDAV] Sync of EteSync failed due to the following error: EteSync (Internal Server Error)

This is similar to the sync issues that I have encountered several times over the past few months, including this issue I previously opened:
https://github.com/etesync/server/issues/146

Dominant language
Python
Stars
332
Forks
61
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from etesync/etesync-dav

All issues in etesync/etesync-dav

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.