Here is an example card from another deck where I was not using the “review ahead” or filtered decks. What is especially strange, is that the intervals appear to be increasing again from TODAY. See screenshot of one example below:
Setting for this deck are as follows:
Note this is a child check of another deck with these options (don’t know if this would affect this but just in case posting):
In both, the custom scheduling is not pictured, but both are empty.
Any idea as to what could stall cards like this on the 2 days interval?
Another example from the same deck shown here:
Notice how the interval decreases from 2023-01-16 @ 10:07 until 2023-02-23 @ 10:12 despite the 3 Ratings and a positive Ease unchanged from 145%. Again, I’m not sure why the intervals are increasing again as of today. The only thing I can think of is I must have set some deck settings between 2023-01-16 @ 10:07 and 2023-02-23 @ 10:12 that caused this decreasing interval behavior. Then sometime between 2023-02-23 @ 10:12 and 2023-03-02 @ 21:03 this was changed to something that no longer caused this decrease.
I believe I had the interval modifier set to something like 0.65 according to what I had read in the manual Is this expected behavior to decrease intervals even when a Good / 3 Rating is selected? This is again why I’d like to see the code governing this calculation/logic.
Starting to get a handle on how the project internal works. I had never used Rust, nor any python+C or otherwise external bindings in python before, so a fair learning curve, but its starting to come around. I was terribly impressed when I asked chatGPT to find where the interval is updated in the github repo, and it pointed me here. A good point to start, but I still needed to understand how the Rust code was bound. It looks like you’re using PyO3 if I’m not mistaken? Happy to try to reproduce this error if I can understand the code base a bit better.