You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…tate (just reset the state/network).
If it can't fetch the results, it now displays a message dialog and only redirects to the landing page after the user clicks OK.
-- #39
We deploy the web app with replicas: 2 in Docker Compose (docker-compose.yml), so it is running two independent instances of the application. Each instance has its own isolated memory space.
When the user submits a job, the request parameters are temporarily saved in a Map object on the server side. Then the saved parameters need to be retrieved in a separate client fetch when the job is finished.
The Map we're using to store the parameters exists separately in each container. If a user's initial job request is handled by one container, and their result request is handled by the other, the second container will not have the job parameters in its Map.
In order to solve this issue, we should store the job parameters in the DB (or use Redis).
Sometimes going to the results page after submitting a gene list does not work -- it goes back to the landing page.
The text was updated successfully, but these errors were encountered: