The error message flashes and disappears immediately. #1516
Replies: 5 comments 1 reply
-
|
I can't reproduce this and must be something with your fork or network setup. As you can see in my video, there is never an error flashing and the network requests never result in status 400. I also noticed you have a different cursor, and it could be due to something in your fork. There is nowhere in the main repo's code base that logs an error |
Beta Was this translation helpful? Give feedback.
-
|
You misunderstood, I didn't say that the LibreChat itself would cause a 400 error. What I meant was, once an error message appears (for example, you can call a non-existent model, like gpt-5 etc.), the error message would flash. The 400 error is just an error I deliberately created. |
Beta Was this translation helpful? Give feedback.
-
|
I indeed forked and made some changes to the UI, logging an error request id is also a msg returned by the base URL I personally used, but these are not important. |
Beta Was this translation helpful? Give feedback.
-
|
Got it, I understand now. "The error message flashes and disappears immediately" did not give me much context and I assumed it was flashing an error at the start of the stream. I'll work on this when I get the chance. This is related to a change made here: #1510 |
Beta Was this translation helpful? Give feedback.
-
|
any ideas on how I can fix it myself? |
Beta Was this translation helpful? Give feedback.
-
|
no need, merging a fix after my next set of changes here. Error handling for the server stream has been tricky but I believe I'm now handling a variety of edge cases while improving UX. |
Beta Was this translation helpful? Give feedback.
-
What happened?
The error message flashes and disappears immediately.
Steps to Reproduce
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions