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
The web UI consistently gets stuck at a certain step, however, the backend logs indicate that this step and the subsequent ones have already been completed
#1511
Open
huoxiao-C opened this issue
Nov 10, 2024
· 3 comments
Describe the bug
We have deployed Chainlit application on the centos server based on Flask, Gunicorn, and Nginx, with the number of worker processes set to 1. Sometimes after asking a question in the web UI, it gets stuck at a certain step such as sql error recognization. However, upon checking the backend logs, we found that this step and the subsequent steps have already been executed. The content displayed in the web UI is as follows.
The text was updated successfully, but these errors were encountered:
SQL issue using persistant storage #922
This issue is similar to yours, involving an SQL problem, but it was closed without any comments or solutions provided.
The web UI might get stuck at a certain cl.step due to issues in the communication between the backend and the UI, particularly with the asynchronous handling of step updates and emissions. This can happen if there is a failure in the asynchronous tasks responsible for sending and updating steps, such as network issues or unhandled exceptions. Ensure that these tasks are correctly handled and that any exceptions are properly logged and managed. Additionally, verify that the context.emitter is functioning correctly and that there are no network issues affecting the communication between the backend and the UI [1].
Describe the bug
We have deployed Chainlit application on the centos server based on Flask, Gunicorn, and Nginx, with the number of worker processes set to 1. Sometimes after asking a question in the web UI, it gets stuck at a certain step such as sql error recognization. However, upon checking the backend logs, we found that this step and the subsequent steps have already been executed. The content displayed in the web UI is as follows.
The text was updated successfully, but these errors were encountered: