Please report any other irregularities here.
Prerequisites: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20130519 Firefox/24.0 Unagi device with MP-dev app installed Steps to reproduce: 1.On desktop and Unagi search for some fully reviewed apps : https://marketplace-dev.allizom.org/app/test-app-freeappfree/ , https://marketplace-dev.allizom.org/app/test-app-forpoland2/ or https://marketplace-dev.allizom.org/app/test-app-forpoland2/ Expected results: Apps are listed in search results Actual results: Apps are not listed in search results
Elastic search had too many files open again (twice this week?) and caused all kinds of bugs. Closing this, reopen if it's still the case.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Verified as fixed . Apps from STRs are now displayed.
Status: RESOLVED → VERIFIED
This bug is reproducible again on -dev . Tried with https://marketplace-dev.allizom.org/app/blesuscrissssreed-4/
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Potentially related to bug 889924?
(In reply to Victor Carciu from comment #3) > This bug is reproducible again on -dev . Tried with > https://marketplace-dev.allizom.org/app/blesuscrissssreed-4/ What did you search for exactly? The logs show that it was approved and then indexed. I see it in the search index. Searching for a prefix, "bles", shows it in the search results.
I can reproduce. Searching for "Blesuscrissssreed" (the app name) returns no results.
(In reply to Matt Basta [:basta] from comment #6) > I can reproduce. Searching for "Blesuscrissssreed" (the app name) returns no > results. I can't: https://marketplace-dev.allizom.org/search?q=Blesuscrissssreed Then I realized I was in region=pl. Is it a payments filter being applied? If so, that's not what this bug was originally about.
This seems like it has to do with the payments filters we apply. Closing as it seems to work as expected. Reopen with STR and notes about regions if this is incorrect.
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago → 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.