Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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
Labels
bug Something isn't working frontend Pertains to the frontend. needs-triage

Comments

@huoxiao-C
Copy link

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.
85C6B849-363D-42b5-A26E-40ACFFAAF73A

Copy link

dosubot bot commented Nov 10, 2024

I found a related issue that might be helpful:

To continue talking to Dosu, mention @dosu.

@dosubot dosubot bot added bug Something isn't working frontend Pertains to the frontend. labels Nov 10, 2024
@huoxiao-C
Copy link
Author

The response is not helpful; it is not related to SQL storage execution error, but rather the web UI gets stuck at a certain cl.step. @dosu

Copy link

dosubot bot commented Nov 11, 2024

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].

To continue talking to Dosu, mention @dosu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working frontend Pertains to the frontend. needs-triage
Projects
None yet
Development

No branches or pull requests

1 participant