ChatGPT, HuggingChat and LeChat Mistral AI's are returning server Errors for trying to analyze large pieces of Text
Categories
(Core :: Machine Learning: General, defect, P1)
Tracking
()
People
(Reporter: rdoghi, Assigned: Mardak)
References
(Blocks 1 open bug)
Details
(Whiteboard: [genai])
Attachments
(4 files)
Found in
- Nightly 129.0a1
Affected versions
- Nightly 129.0a1 (2024-07-02)
Affected platforms
- All
Steps to reproduce
- Reach about:preferences#experimental page.
- Enable the AI Chat integration.
- Select the HuggingChat AI provider.
- Reach the following page: https://mistral.ai/terms/#terms-of-service-le-chat
- Analyze a large piece of text.
- Change the AI provider to leChat Mistral AI.
- Analyze the same piece of text.
Expected result
- Either a Normal Error should be displayed for the users that exceeded the maximum number of character allowed to be analyzed in one go, or the Text should be analyzed by the AI engine.
Actual result
- The AI chat panel returns an invalid Error response.
The Ai panel returns a Bad Request error.
The ChatGPT and Gemini have no problems analyzing the same exact piece of text.
Regression range
Not a regression.
| Reporter | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
Did the fix from bug 1903900 avoid server error with huggingchat but still there for lechat?
| Assignee | ||
Comment 3•1 year ago
|
||
This same issue probably results in chatgpt showing a blank page with a server error since bug 1903900
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
bug 1903900 should have fixed this for huggingchat
| Reporter | ||
Comment 6•1 year ago
|
||
The issue still occurs for hugging chat in our latest Nightly 133.0a1 (2024-10-10)
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 7•1 year ago
|
||
Refactor length calculation with even more conservative adjustment as prefs. Point to copilot instead of bing but still hidden.
Updated•1 year ago
|
Updated•1 year ago
|
| Reporter | ||
Comment 10•1 year ago
|
||
Verified as fixed in our latest Nightly build 133.0a1 (2024-10-20)
Comment 11•1 year ago
|
||
The patch landed in nightly and beta is affected.
:Mardak, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox132towontfix.
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Description
•