pimutils / pimutils/vdirsyncer

Unknown error occurred: DAVSession.__init__() missing 1 required keyword-only argument: 'connector'

Open
#1,019 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Before you submit bug reports: https://vdirsyncer.pimutils.org/en/stable/contributing.html

Things to include in your bugreport:

  • Your vdirsyncer version 0.19.0
  • If applicable, which server software (and which version) you're using ownCloud 7.0 (yes, the server is ancient CentOS 6)
  • Your Python version 3.10.9
  • Your operating system openSUSE/Factory (I am actually an employee of SUSE working on packaging Python modules)
  • Your config file
  • Use vdirsyncer -vdebug for debug output. The output is sensitive, but
    please attach at least the last few lines before the error (if applicable),
    censored as necessary. This is almost always the most useful information.
 $ vdirsyncer -vdebug repair matej_calendar_remote/personal
warning: This operation will take a very long time.
warning: It's recommended to make a backup and turn off other client's synchronization features.
Do you want to continue? [y/N]: y
debug: Fetching value for password.fetch with shell strategy.
Discovering collections (skipping cache).
error: Unknown error occurred: DAVSession.__init__() missing 1 required keyword-only argument: 'connector'
error: Use `-vdebug` to see the full traceback.
debug:   File "/usr/lib/python3.10/site-packages/vdirsyncer/cli/__init__.py", line 32, in inner
debug:     f(*a, **kw)
debug:   File "/usr/lib/python3.10/site-packages/vdirsyncer/cli/__init__.py", line 271, in repair
debug:     asyncio.run(main())
debug:   File "/usr/lib64/python3.10/asyncio/runners.py", line 44, in run
debug:     return loop.run_until_complete(main)
debug:   File "/usr/lib64/python3.10/asyncio/base_events.py", line 649, in run_until_complete
debug:     return future.result()
debug:   File "/usr/lib/python3.10/site-packages/vdirsyncer/cli/__init__.py", line 264, in main
debug:     await repair_collection(
debug:   File "/usr/lib/python3.10/site-packages/vdirsyncer/cli/tasks.py", line 118, in repair_collection
debug:     async for config in cls.discover(**config):
debug:   File "/usr/lib/python3.10/site-packages/vdirsyncer/storage/dav.py", line 484, in discover
debug:     session, _ = cls.session_class.init_and_remaining_args(**kwargs)
debug:   File "/usr/lib/python3.10/site-packages/vdirsyncer/storage/dav.py", line 371, in init_and_remaining_args
debug:     return cls(**self_args), remainder
 $ 

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

Start at vdirsyncer/storage/dav.py, especially DAVSession initialization in init_and_remaining_args and discovery. Reproduce with vdirsyncer -vdebug repair matej_calendar_remote/personal using the attached configuration, then verify discovery no longer raises the missing connector argument error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.