Syncing fails when depending on which deck is selected, works after changing selection about ankicommunity-sync-server HOT 3 OPEN

After some more experimentation, I've been noticing this happens also when certain subdecks are in focus, but when I change the focus to the parent deck the problem goes away. So it's probably not due to just selecting a newly created deck. Still not sure what the exact trigger is.

from ankicommunity-sync-server.

the same problem as yours on my windows Anki. select Anki2.1 exprimental V2 scheduler checkbox in the preference-->scheduling algorithm.Then the dialog screen will disapear.yet whether syncing succeeds or not is unknown.

from ankicommunity-sync-server.

Look like the current deck id in anki-sync-server will be updated by client current deck when you client modify time is newer that server's modify time. If you client older, then will have this bug. This bug is fixed in pr #52. But as a workaround, you can select any deck meaning you update the client modify time to latest,so you current deck info will be sync to server,and avoid this issue.

As for the next subdeck issue,
the nest subdeck issue is that ankisyncserver duecounts output [[0, 0, 3] by self.col.decks.find_deck_in_tree which is recursive find the deck id,but for Anki desktop ,[0, 0, 0], is created by add_due_counts which use the get_subnode func not as a recursive func. So the duecounts will different.
see align rslib get_subnode impl with anki pythonapi find_deck_in_tree #805
https://github.com/ankitects/anki/pull/805

Same machine ,same pyenv.
Anki-sync-server master using master 2.1.36 anki and ankirspy python package.
ANki Desktop 2.136 master.
Anki android 2.13.5.
Exprimental V2 scheduler
Now almost no any problem.

from ankicommunity-sync-server.