Users are experiencing an issue where the user list remains empty on a fresh Discourse installation, even after creating multiple users. elliem reports the problem occurs regardless of login status and with users of various trust levels. cpradio and zogstrip explain that the directory page is updated by a background job, which may not have run yet, and that the page is heavily cached. sam confirms this is working as designed, with a delay. duranmla seeks a way to force the job in a development environment, and pfaffman identifies the relevant jobs as Jobs::DirectoryRefreshDaily and Jobs::DirectoryRefreshOlder. The discussion is categorized as a feature request, acknowledging the delay but noting the complexity of reducing it.
I have a fresh Discourse installed on DigitalOcean (followed ssh instructions)
After creating 5 users, and visiting /users page it always “No results were found.”
What could be wrong? This happens for both logged in and logged out users. Also settings box is ticked to show users list.
What TL are the new users? I believe it filters out TL 0 users. Plus that page is very heavily cached and requires a job to run in Sidekiq (IIRC)
They are a mix of users. Some are even admins.
Like @cpradio said this page is updated in a background job. I would ensure sidekiq is properly running and wait for 24 hours for the job to run.
Reclassificando como Contribute > Feature. O comportamento está conforme o esperado, há um atraso envolvido. Se você deseja que seja mais rápido, isso acarreta um custo elevado e complexo.
Is it there a way to force that background job to run on a local setup? I have the same issue in my development environment I have added few users to different levels also make those users create some topics but my users list its empty.
Of course, tomorrow may get solved, but other fellows may need this in order to develop something and it will be annoying try to wait for such long time.
Cheers!
Você pode dar uma dica de qual é o trabalho para que eu possa forçá-lo? Já examinei /sidekiq/scheduler e app/jobs e ainda não consegui encontrá-lo.
E, depois de confirmar que isso funciona no ambiente de teste, se um cliente corporativo quiser que seja executado, eles podem enviar um pedido por e-mail para o suporte?
EDIT: Encontrei: Jobs::DirectoryRefreshDaily
Mas /u ainda não está listando todos os usuários ativos.
EDIT: Veja também Jobs::DirectoryRefreshOlder
