I’m not sure whether I’m the first one who notice this problem and post it here.
To reproduce bugs, I often create a new profile and import decks with scheduling info submitted by users.
The due is a offset based on the creation stamp. Obviously, the new profile’s creation stamp is newer than the user’s original collection’s. So all cards’ due will be shifted. In this process, some due’s values become negative.
It causes some problems:
- Some functions only accept unsigned integers for the ‘due’ parameter, which induces unrelated bugs. It makes the deck useless for reproducing some specific bugs.
- Some users may move their old decks to a new profile. Then some functions will not behave as expected.
Here are my suggestions:
- Ask for collection file instead of deck file with scheduling info to reproduce bugs, particularly when the bug is related to scheduler.
- Don’t separate your profile via export/import decks with scheduling info.
- Maybe we need to refactor some functions to accept negative due.
@dae what do you think?