pimutils / pimutils/vdirsyncer

Can't delete an event from NC -> Google

Open
#955 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.9k
Forks
185
Avg merge
11h 49m
Merged PRs (30d)
1

Description

I'm running vdirsyncer v0.18 on Python 3.7, in a virtual environment on shared hosting.

The sync function works as expected, with one exception. If I create a new event on nextcloud, it will upload to google no problem. But then if I go and delete that event from Nextcloud, it will throw and error next time it syncs saying that it can't find the event in Nextcloud as it's trying to sync the google event.

Unknown error occurred for doublecloud/mygoogle: 400 Client Error: Bad Request for url: https://mynextcloud.com/nextcloud calendar 1/b54fcf03-3dd3-47e7-ab26-004536b109bb.ics error: Use -vdebug to see the full traceback.

The error is resolved by manually deleting the event from google.

This is my config

I've also tried playing with different conflict resolution options, with no success.

[general]
status_path = "~/.vdirsyncer/status/"
#CALDAV
[pair doublecloud]
a = "my_nextcloud"
b = "my_google"
collections = [["mygoogle", "nextcloud calendar 1", "gcal1"],["fbgoogle", "nextcloud calendar 2", "gcal2"]]
metadata = ["color"]

[storage my_nextcloud]
type = "caldav"
url = "https://mynextcloud.com/remote.php/dav"
username = "my_username"
password = "redacted"

[storage my_google]
type = "google_calendar"
token_file = "~/vdirsyncer/google_token"
client_id = "851472075362-o0g840egsuo4kj9lvahsub765floeh7c.apps.googleusercontent.com"
client_secret = "redacted"

Contributor guide

Open the 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.

Research direction

The issue names no source files or tests. Start by reproducing the Nextcloud-to-Google sync with a newly created event, then delete it from Nextcloud and inspect the verbose traceback and deletion handling. Done means a deleted Nextcloud event no longer causes the next sync to fail while leaving the corresponding Google event behind.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.