Closed snowtimeglass closed 2 years ago
Long time no see @snowtimeglass :-), thanks as always for a thorough bug report. Now if only you would log things that looked easier to fix ;-)
What does Anki Desktop show here (for the same cards)?
Long time no see @mikehardy @david-allison :-), thank you so much for the wonderful progress.
@mikehardy
Now if only you would log things that looked easier to fix ;-)
Excuse me, but I'm not sure what you meant. Did you mean that if only more information would be added? :-)
@david-allison
What does Anki Desktop show here (for the same cards)?
I should have specified that point. Anki Desktop shows consistent intervals properly. Examples (of Anki Desktop and AnkiDroid) are as follows. They are the results of the third study of the above sample card.
I'm not sure what you meant
I just meant scheduler bugs are usually hard! Much easier when something is just the wrong color. But better to know there is a problem then not, of course, I was just joking and always appreciate the reports
Thanks. I was not so sure of that, but felt you were just joking, so please don't worry :-) I always appreciate your arduous work, too.
Thanks so much, so it appears to be a display bug in CardInfo
.
This is a massive relief: this implies a bug in some quick code that I wrote, rather than a bug in the scheduler. We will be replacing CardInfo
entirely with Rust.
Thanks, I'm glad to hear that :-)
By the way, I just now unexpectedly saw #7762 (a CardInfo
topic) and remembered it. How about reopening it?
Reopened! To be honest, I expect it'll go stale again, but more than happy for someone to pick it up as side work
In general, my plans are:
Thanks! I hope your plans will go well.
@david-allison can i work on this issue
@david-allison can i work on this issue
Yep! Thanks!!
@Prince-kushwaha, Are You Still Working On This Issue?
@david-allison @mikehardy I have a question related to this issue, I was working on this issue before it was assigned, and was checking for the possible errors in the main code. So I searched for possible errors in the "HARD" button part, as well as for the display part in the "card info". And the result, I didn't find any errors in both. In this process I found out that they were connected through the database (as per my knowledge, its referenced as this).
So, I know its possible that I might have missed the wrong code in the searched files, but is there a chance that the bug is in the database ?
@Arthur-Milchior , would you answer the previous question i.e. ...is there a chance that the bug is in the database ?
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically
@suman-somu (if you are still interested) Essentially, we don't know. We didn't investigate in depth this bug, we had and still have more urgent things to do. The bug can be anywhere, in the database, in the scheduler code, in the display code. Discussion above concluded it was in the display code, so that's personally where I'd start looking. But if this analysis was wrong, you can do your own investigation and try to find why. In particular, you may want to learn how to read the database content directly, e.g. with sqlitebrowser on your computer, so that you can check the actual value and compare it to the displayed value. You may want also to use the same collection on anki and ankidroid, so they should have the same database content and this should allow to confirm whether the value displayed is different on both devices
Okay, I will go through it again thoroughly.
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically
I have confirmed that this issue remains on 2.16alpha83, so please keep this open.
AnkiDroid button : 32 min AnkiDroid Card info : 3 min Anki Desktop button : 3m Anki Desktop Card info : 3 minutes
@snowtimeglass does this happen if you alter settings --> advanced --> enable new backend + enable v3 scheduler?
Ah, this doesn't happen in these settings! Thanks for the advise!
Okay - we are moving towards that as the default hopefully soon, so this may be considered a low priority in my opinion. If we fixed it, we would be working on code that will soon be deleted, so it is not worth a lot
Well noted :-)
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically
Thank you always, developers.
Reproduction Steps
(In short, answer with "HARD" button, then display "Card info" of the card.)
Expected Result
The interval written in the study row is consistent with the one written in the "HARD" button.
Actual Result
The interval written in the study row is inconsistent with the one written in the "HARD" button.
Another example
Debug info
AnkiDroid Version = 2.16alpha49
Android Version = 9
Manufacturer = OPPO
Model = CPH1983
Hardware = qcom
Webview User Agent = Mozilla/5.0 (Linux; Android 9; CPH1983 Build/PKQ1.190519.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/99.0.4844.58 Mobile Safari/537.36
ACRA UUID = 3b6235a2-041c-45f0-a6d1-782c54c43431
Scheduler = std2
Crash Reports Enabled = true
DatabaseV2 Enabled = true