epic: Better Error Handing

[imtuyethan]

Motivation

The current error handling system in Jan app has too many edge cases, which is challenging to maintain.
Our goal is to implement a simplified, standardized error format within the Jan app, focusing on improving maintainability, and providing better context for error handling.

Key Results

• Less hassle: We'll save time by using a standard template instead of creating unique messages for each scenario.
• Efficient troubleshooting: Standardized messages speed up troubleshooting for both users and platform.

Key User Stories

• Users should see a clear & standardized error message
• Users see inline error message in threads
• Error message should be saved in threads so users can look back when they need to
• Users can copy logs & file Github issue or send it to our Discord
• Errors type:
  • For unclear errors, there’s no error code
  • For identified error, we map it with error code
• All errors should be mapped out with recommended docs

See error code numbering convention: https://www.notion.so/jan-ai/Error-Code-Numbering-Convention-a3a1e96a93254df3ace6dc93d4cc849e?pvs=4

Specs

Check Notions spec for more details
https://www.notion.so/jan-ai/Standardized-Error-Format-for-Jan-abea56d32d6648bb8c6835f9176f800c?pvs=4

Designs

Figma

[imtuyethan]

Related issues that needs better error handing:

1. Jan fails to load models when the file path contains special characters: https://discord.com/channels/1107178041848909847/1294680372264697907
2. Missing Hardware Dependencies → Ask users to download dependencies to turn on GPU acceleration: feat: Implement UI for Better Hardware Settings  #3688
3. feat: Graceful failure for model loading (not Something's Amiss Error) #3517

[freelerobot]

Handled by cortex, this issue is a UI/design issue, which we need to rework