Open JeongYunLee opened 1 month ago
Now, I'm not sure this is an OAuth problem. When I used just @cl.password_auth_callback
without @cl.oauth_callback
, I got the same error.
Plus, I'm using langgraph with chainlit and this error occurs irregularly. For example, (it's not clear) when the answers' lengths are long, the error occurs even if the processes are same.
Is there anybody who got the same error? please share your ideas... thanks
Describe the bug I used Google OAuth for data persistence, and the login process worked correctly. However, after performing a query and getting a response, I continuously encounter the error “Not Found. Thread not found” during the process of saving the log on the left side. The
@cl.oauth_callback
function I used is as follows.I discovered a similar issue but couldn't find a solution, so I created a new issue.
To Reproduce Steps to reproduce the behavior:
@cl.oauth_callback
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
chainlit == 1.1.400
Smartphone (please complete the following information):
Additional context
I am using the
@cl.password_auth_callback
function for login instead of OAuth, and in this case, the same error "Not Found. Thread not found" occasionally occurs (but not always). Could the irregular occurrence of this error indicate that the cause is unrelated to OAuth authentication?