Skip to content

Worker runs are not loaded if the corpora take too long to load

  1. Take a TGV and use the onboard Wi-Fi, or go to some random café with Wi-Fi, or use TurbineVisiteur, or go to your grandparents' house with the 56K modem.
  2. Create a process and add some worker runs.
  3. Press F5 on the worker run configuration page, or go to the /process/<id>/configure page, by typing the URL in the address bar.
  4. You may initially get "You do not have admin access to this process." because the frontend has not finished fetching all corpora.
  5. A "This process does not have any worker runs." notification is shown.
  6. Cry.
  7. Click on View process elements.
  8. Click on View workers to go back to the worker runs page.
  9. Some wild worker runs appear!

This happened almost all the time for me in prod and demo, and happens randomly in preprod. There are over 500 corpora in demo, so ListCorpus can get pretty slow. Somehow, opening the Firefox dev tools in prod and demo made the bug disappear, but on both Firefox and Chromium and on all instances, using the slow network modes in the dev tools made the bug appear all the time.