Do you mean that every time you re-optimize parameters, your number of due cards changes? I don’t have that problem, that’s definitely not the intended behavior.
I noticed some of the FSRS tool tips in the English Anki use hyphens “-” for sentence breaks. As far as I know em-dashes “—” should be used for sentence breaks instead, though in the UK en-dashes “–” are sometimes used as well. The two places where I noticed this is in deck-config-desired-retention-tooltip and deck-config-compute-optimal-weights-tooltip in deck-config.ftl in the anki-i18n repo. For me it would be easiest fixing that with a PR but I guess since it’s i18n I should do so in the translation interface, though I don’t have an account there yet (maybe will request one, can help translate German after all.)
Since the release of 23.10 multiple users reported to me that suddenly their new cards and reviews are being mixed up. They had Anki set up in such a way that reviews come first and only after they are done with them, new cards should appear. Seems to happen on Mac and AnkiMobile (iPad). Will look into it myself after this, just wanted to let you know right away because of the impending release.
@basiskarten, check Due cards not showing up at all : apparently that user had it caused by “AMBOSS Official Medical School Step Shelf Study Resource”.
That seems to be a different issue. My users are law students, so they wouldn’t use this add-on. Plus their issue is just the order of when new cards and reviews are being shown.
@basiskarten Are they using v3 or v2? What scheduler did they use before? Akaik Anki changed the default scheduler from v2 to v3 in release 23.10, though still both are available. In v3 the new/review order is set in the deck options, so you can change it on per-preset-basis. I didn’t use v2 in a while (was an early v3 adopter) but I think it might have been a global option back then.
Anyway, if they have the v3 scheduler enabled in the deck preferences, the solution is likely to click the gear icon next to the deck to open the deck-present options, go to the “Display order section” and set the “New/review order” setting according to preferences.
Btw, I agree that maybe it would be nice that upon changing the scheduler from v2 to v3, if Anki could inherit the default deck option from the previous global option. But I’m not sure if that would be easy to implenment.
1 Like
In 23.10 they must be using v3 since support for v2 was dropped in this release. So far after looking into it I couldn’t reproduce the issue, with the following settings it works as expected:
Will update when I hear back from them. Thank you for your input!
Ah, I totally forgot it was dropped not just that the default was changed. I’m also just a user 
.You settings seem sensible (I’m also German so I don’t mind German screenshots). One more pitfall might be with subdecks.If super- and sub-decks have different review order settings, and you study the subdecks, than the order in the subdecks settings is ignored and only the order specified in the superdeck is used. But tbh I don’t think that this is likely the problem.
1 Like
rc3 contains some last-minute security fixes. I’d greatly appreciate it everyone could give it a try before a stable release tomorrow, to ensure there haven’t been any unintended regressions.
Personally, I’m in the “straight quotes and hyphens have buttons on my keyboard, and convey the same meaning” camp, but I know some people care about this more. While I wouldn’t necessarily object to a PR that changes the existing strings, I’m afraid I’d probably continue my old habits for future strings, so I’m not sure what would be the better option - keeping things consistent, or having a mix of the two styles. If you were to make a change, it would only need to be made to Anki’s repo, as it would automatically get transferred to the translation site.
1 Like
@dae Regarding the dashes, that’s just my nitpicky habit from scientific writing in LaTeX, where I just use two hyphens in the source code -- (which solves the issue with buttons on the keyboard) and from editing Wikipedia. I have my editor set up in a way that it’s simple to add unicode symbols, but I admit I can’t expect that from every contributor.
To be honest in technical documentation I don’t care about typography, only it’s something that is published (e.g. for print) I care very much, but for software I’m not sure. It’s still kind of publicly user-facing, but not a journal paper .
I already created the PR anki-core-i18n #9 before I saw your reply here, feel free to close it.
Regarding allowing users to set desired retention as high as 0.99, is it implemented? I don’t see it in the changelog.
I’m getting this error (on Ubuntu 23.10):
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "aqt", line 46, in <module>
File "anki.lang", line 12, in <module>
File "anki._backend", line 48, in <module>
Exception: rsbridge and anki build hashes do not match:
af3a2d39 vs 2241d2fd
Hi, after updating to 23.10 (Linux), I get a message every few minutes (around 15-30):
A network error occured.
Error details: error sending request for url(): error trying to connect: tcp connect error: Connection refused (os error 111).
I use the “Self-hosted sync server” (Options->Syncing).
The message only appears when the built-in server anki --syncserver is not running.
I’ve checked with all the add-ons disabled. It appears that Anki attempts to connect to the server periodically, and when the server is turned off at that moment (I only enable it for synchronization), the message from the picture pops up. It’s quite bothersome because it takes the window focus every few minutes.
I put deck:my deck name with spaces into the FSRS query, and it just said “Error: 500: Insufficient review history to perform this operation.”
It should probably say that the deck does not exist if the query returns no results, be it there or in the Browser.
Version 23.10.1 rc3 Windows 10 qt6.6, no add-ons
When I open the Reviewer and every time I rate a card, Anki shows these warnings:
Error: 403: <!doctype html>
<html lang=en>
<title>403 Forbidden</title>
<h1>Forbidden</h1>
<p>You don't have the permission to access the requested resource. It is either read-protected or not readable by the server.</p>
Unexpected API access. Please report this message on the Anki forums
The problem seems to occur only when using my main profile. It does not seem to be influenced by the note type or the deck. Checking the database, restarting Anki/my computer didn’t help.
The main thing that comes to my mind that differentiates this profile from the others is that this is the only one that I synced using AnkiDroid 2.17alpha3. IIRC the problem didn’t occur when I first started using rc3.
Tried checking what the Console says:
Anki starting...
Initial setup...
Running with temporary Qt5 compatibility shims.
Preparing to run...
Qt debug: doh set to "" -- SystemOnly
Starting main loop...
Not found: _MaterialIcons-Regular.woff2
Not found: _MaterialIcons-Regular.ttf
Not found: _MaterialIcons-Regular.woff
JS error /_anki/js/reviewer.js:440 Uncaught (in promise) Error: 403: <!doctype html>
<html lang=en>
<title>403 Forbidden</title>
<h1>Forbidden</h1>
<p>You don't have the permission to access the requested resource. It is either read-protected or not readable by the server.</p>
JS error /_anki/legacyPageData?id=1807788353280:3 Uncaught TypeError: Cannot read properties of undefined (reading 'setAttribute')
JS error /_anki/js/reviewer.js:440 Uncaught (in promise) Error: 403: <!doctype html>
<html lang=en>
<title>403 Forbidden</title>
<h1>Forbidden</h1>
<p>You don't have the permission to access the requested resource. It is either read-protected or not readable by the server.</p>
Uninstalled and reinstalled rc3 and the problem still occurs. Switched back to rc2 and everything seems to work fine.
Update: As Damien suspected this was fixed by specifying the correct deck options (and applying them to all subdecks). I found it somewhat reassuring that even power users like Arthur Milchior were confused by this. 
Thanks to those who tested. I’ve just pushed out rc4 which should hopefully address the issues people ran into. I’ll give it a day or two before a stable release.
If you don’t have the server running permanently, you can turn off automatic media syncing in the preferences.
Yes, which you should be able to confirm if you test the rc 
3 Likes
rc4 solves the problem I reported. 
The problem regarding the reviewer the I had reported seems to be fixed.
I suggest keeping “toggle masks” even in “Hide One, Guess One” mode when there are text masks (i.e., one or more {{c0:: }} clozes)