-
Notifications
You must be signed in to change notification settings - Fork 81
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
Sync crashes after deck deletion #28
Comments
Just confirmed that the sync also crashes if you have deleted any cards. To replicate, delete a card, and then try to sync:
|
cecini
added a commit
to cecini/anki-sync-server
that referenced
this issue
Oct 30, 2020
…ntruduced after 3.1.28 f592672fa
cecini
added a commit
to cecini/anki-sync-server
that referenced
this issue
Oct 30, 2020
in the server,need update graves usn as maxusn avoid sync serve log: sanity check failed with server: graves had usn = -1 such as issue ankicommunity#28 second comment
Applying PR code now works well |
cecini
added a commit
to cecini/anki-sync-server
that referenced
this issue
Nov 3, 2020
the change intruduced after 3.1.28 f592672fa
cecini
added a commit
to cecini/anki-sync-server
that referenced
this issue
Nov 3, 2020
once client items in graves have been remove in the server,need update graves usn as maxusn avoid sync serve log: sanity check failed with server: graves had usn = -1 such as issue ankicommunity#28 second comment
cecini
added a commit
to cecini/anki-sync-server
that referenced
this issue
Nov 3, 2020
in the server,need update graves usn as maxusn avoid sync serve log: sanity check failed with server: graves had usn = -1 such as issue ankicommunity#28 second comment
VikashKothary
added a commit
that referenced
this issue
Nov 15, 2020
Fix the remove deck lead server crash issue #28
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction steps:
I'm using Anki desktop 2.1.33. Upon sync, the dialogue box pops up:
Here's the traceback from the server:
The text was updated successfully, but these errors were encountered: