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
An "unsafe character" (+) seems to be derailing the sync process when syncing with Google. #865
Comments
I have exactly the same error with WEBEX meetings |
I have this exact error with WEBEX meetings as well. In #491 an "unsafe character" error was fixed by removing it from the reserved char list. I tried that here, removing the + from line 29 of dav.py, but now I get a new error:
|
I have this too ... fortunately I don't have too many webex meetings. It was pretty impossible to find the offending calendar entry by searching, but fortunately I noticed my calendars were not syncing within a few days of accepting a webex meeting, so it it was easy to find the entry. It would be nice to see a fix that works since this is the only thing that derails my sync. |
Can you check if you have the same issue with the current master? I believe this is fixed via #929.
|
Before you submit bug reports: https://vdirsyncer.pimutils.org/en/stable/contributing.html
Things to include in your bugreport:
0.16.8
Python 3.7.9
alpine docker container on ubuntu
vdirsyncer -vdebug
for debug output. The output is sensitive, butplease attach at least the last few lines before the error (if applicable),
censored as necessary. This is almost always the most useful information.
There was a debugging note right before the error regarding an "unsafe character" which is the + symbol translated into %2b. I included snippets of the debug output surrounding the offending character. Ellipses show gaps (that I would think are fairly irrelevant) cut out.
Reading the output, it seems the href cant be found. Is that because the href is using the encoded character? Any ideas on how to resolve the issue?
The text was updated successfully, but these errors were encountered: