-
-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Number of strings changes when changing ordering #5105
Comments
I can't reproduce it - it still shows same number. What might have happened: The search result is cached in session for a user to give consistent results while he is changing the strings (otherwise translated strings would disappear from the search). Changing the sort order stops using the cache and fetches the data from the database. Not sure if we can do something effective to address this. |
Mobile version, android 9, I haven't tried for pc. |
The problem occurs after translating several segments. You have to translate a few segments, stop the translation and come back to it. After sort change, the initial (greater than current) number of segments is loaded. It looks like it's reading from the cache. After a few hours, the number of segments is up-to-date. |
That's the issue I've described in #5105 (comment). The list of matching strings is fetched first time the query (including ordering) is used. You then browse the cached result to be able to go to previous strings which might no longer match the conditions. The solution might be to reuse the existing cached string list when changing ordering. |
Describe the bug
Incorrect number of empty strings after using the "Number of words" sort.
To Reproduce the bug
Description should look similar to this:
Steps to reproduce the behavior:
Screenshots
The text was updated successfully, but these errors were encountered: